change to JTA transaction configuration --------------------------------------- Key: JBPM-901 URL: http://jira.jboss.com/jira/browse/JBPM-901 Project: JBoss jBPM Issue Type: Task Components: Core Engine Reporter: Tom Baeyens Assigned To: Tom Baeyens Fix For: jBPM jPDL 3.2 change from CMT to JTA transaction configuration to enable both the EJBs and the webapp to leverage the same JbpmConfiguration. For this I created a new persistence service called JtaDbPersistenceService. It verifies that there is an active UserTransaction during the JbpmContext block. If not, one is created and ended in the jbpmContext.close. So now in the EJBs (CMT) there is already a transaction in progress and the JtaDbPersistenceService will not do anything. For the webapp, there will not be a user transaction and hence JtaDbPersistenceService will begin and end the user transaction. This approach was needed because hibernate doesn't support beginning and ending of user transaction. regards, tom. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira