So, we came up with a workaround that was really easy to implement. Basically, you need to turn off the audit trail while updating the values. After looking into it, we noticed that the AuditableAspect class has a method onUpdateAudit(NodeRef nodeRef) that is called every time the document is saved. We wrote a class that extends the AuditableAspect and basically skips over the updating of the audit trail when you change properties:
package com.tsgrp.alfresco.repo.audit;
import org.alfresco.repo.audit.AuditableAspect;
import org.alfresco.service.cmr.repository.NodeRef;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
public class CustomAuditableAspect extends AuditableAspect {
// Logger
private static final Log logger = LogFactory.getLog(CustomAuditableAspect.class);
private boolean runSuper = true;
public void setRunSuper(boolean value) { this.runSuper = value; }
/**
* Maintain audit properties on update of node
*
* @param nodeRef the updated node
*/
public void onUpdateAudit(NodeRef nodeRef)
{
logger.debug("In CustomAuditableAspect.onUpdateAudit(NodeRef nodeRef)…>");
if (this.runSuper) {
logger.debug("…>");
super.onUpdateAudit(nodeRef);
logger.debug("…>");
}
logger.debug("…done.");
}
}
We then updated the core-services-context.xml in [ALF_HOME]/tomcat/webapps/alfresco/WEB-INF/classes/alfresco to point to our CustomAuditableAspect instead of the OOTB one and spring inject a boolean:
<beans>
…
<!– Audit –>
<bean id="auditableAspect" class="com.orbitz.alfresco.repo.audit.OrbitzAuditableAspect" init-method="init">
<property name="nodeService">
<ref bean="dbNodeService" /> <!– bypass loads of interceptor layers –>
</property>
<property name="policyComponent">
<ref bean="policyComponent" />
</property>
<property name="authenticationService">
<ref bean="authenticationService" />
</property>
<property name="tenantService">
<ref bean="tenantService"/>
</property>
<property name="runSuper" value="false">
</bean>
…
</beans>
In our case, we're doing a one time migration and only need to set this property once on the document. After the migration, we'll flip the boolean back to true as we want the audit trail to continue and restart Alfresco. Otherwise, the modified date and modifier properties will never update unless manually changed.There's probably a better way to do this, but hopefully this gets some people going.
