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.