the usertransaction is eventually bound to the jndi tree.
The problems seems to be is that the 'WorkflowService' is commencing *before* the
hibernate service has bound the usertransaction to the jndi tree.
i confirmed this by placing trace inside the workflow service code and the userTransaction
is only bound some time after the workflow service has commenced. werid i know.
i have no understanding how the hibernate service starts and it role in the user
transaction/jndi binding.
i dont know what differences between jbpm3.2.2-jbpm3.26 would cause such behaviour.
-lp
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248298#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...