[jbpm-issues] [JBoss JIRA] Created: (JBPM-2339) Complete JTA transaction refactoring

Complete JTA transaction refactoring ------------------------------------ Key: JBPM-2339 URL: https://jira.jboss.org/jira/browse/JBPM-2339 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Bernd Ruecker Assignee: Tom Baeyens Priority: Critical Fix For: jBPM 4.0 After the JTA refactoring there are two problems left which have to be fixed. 1.) The JtaTransactionInterceptor should work even if there is already running JTA transaction. Currently a exception is thrown that there is a transaciton ACTIVE. Instead of that it should just use it and do not create a own one. 2.) Suspending the transaction shouldn't be done in JtaTransactionInterceptor like it is done at the moment. The use case is to support nested transactions for the job executor (where it decrements the counter and maybe stores exceptions). The necessary code should be placed in the JobExecutor (so it should use Transaction.suspend directly), so it is at the right place. The current implementation with suspending every COMMITTED transaction it finds in the JtaTransactionInterceptor is hacky. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira