Hi Zac, then I don't understand your problem. If the processInstance is being commited (persisted) that should be what you are expecting or isn't it? If the processInstance is persisted the surrounding cmt commited and everything is fine.
If you trace the jbpm / hibernate code you will see some magic going on that figures out in what kind of environement everyting is happening. JBPM 'transactions' are not J2EE transactions. If called inside an existing transaction they will only flush the session and leave everything else to the existing transaction. The upside of this is that you can use the same code in various envs without changing anything. So it isn't illegal as it doesn't realy begin or commit a transaction. Greetings Rainer View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3915676#3915676 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3915676 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
