topic Externalizing Transaction Management for Activiti in Alfresco Archive

Externalizing Transaction Management for Activiti

aseem — Tue, 25 Mar 2014 14:58:26 GMT

Hi,Is there a way to tell Activiti to use an external transaction manager for managing transactions within a bean? I've gone through the documentation and other posts on this forum and it seems like if we mark our UserBean with @Transactional (Spring annotation) and set transactionsExternallyManaged

Re: Externalizing Transaction Management for Activiti

jbarrez — Tue, 01 Apr 2014 17:40:15 GMT

That is indeed the way to do it: create a custom config and let you be inspired by the the SpringEngineConfiguration.
The bulk of the work will probably be the interceptor responsible for starting/committing the transaction.

Re: Externalizing Transaction Management for Activiti

aseem — Tue, 01 Apr 2014 21:30:47 GMT

Thanks Joram, will try to implement and let you know how it goes. Alternatively, will let you know in case I get stuck

Re: Externalizing Transaction Management for Activiti

aseem — Tue, 28 Oct 2014 18:00:47 GMT

I was successful in doing this (which was a while ago) and sharing the solution in case someone else runs into this kind of a problem. Its a bit late, especially since 5.16 was released which handles this in a very graceful manner.

Had to create a CustomProcessEngineConfiguration class that extends ProcessEngineConfigurationImpl and overrides createTransactionInterceptor() and buildProcessEngine() methods.

<code>
@Singleton
public class CustomProcessEngineConfiguration extends ProcessEngineConfigurationImpl
{
    @Override
    protected CommandInterceptor createTransactionInterceptor()
    {
        return new TransactionInterceptor(this.getDataSource());
    }

    @Override
    public ProcessEngine buildProcessEngine()
    {
        return super.buildProcessEngine();
    }
}
</code>

The TransactionInterceptor class extends AbstractCommandInterceptor (for 'next' variable to execute the transaction chain) and implements org.aopalliance.intercept.MethodInterceptor. The overridden invoke(MethodInvocation invocation) method is what manages the starting and committing of transactions or rolling back in case of failure. In my case, it was as easy as looking at methods which have @com.google.inject.persist.Transactional annotation on them and wrapping them up in one transaction in the invoke() method.

On definition side, setting transactionsExternallyManaged to true in activiti.cfg.xml and creating process engine as:

<java>
ProcessEngine processEngine = CustomProcessEngineConfiguration
                .createProcessEngineConfigurationFromResource("activiti.cfg.xml")
                .setDataSource(dataSource)
                .buildProcessEngine();
</java>

did the trick.

Re: Externalizing Transaction Management for Activiti

jbarrez — Fri, 31 Oct 2014 15:13:44 GMT

Thanks for posting back, even after this time 🙂