Hi Ranier, anonymous wrote : f the processInstance is being commited (persisted) that should be what you are expecting or isn't it? Yes I expect the processInstance to be committed when flush/commitTransaction is invoked.
I don't think I should have to call session.flush() or jbpmSession.commitTransaction() as this Hibernate documentation http://hibernate.org/42.html#A7 states: anonymous wrote : Hibernate binds the current Session to the current (JTA) system transaction that is controlled by your EJB transaction assembly. When the system transaction commits (the EJB transaction completes), the Session is automatically flushed and closed. | Is this wrong? Another question: If I end the jbpmSession.commitTransaction(), then if I call the SSB's sessionContext.setRollbackOnly() method shouldn't any updates/inserts performed by Hibernate be rolled back? Thanks for your time. Zac View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3915696#3915696 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3915696 ------------------------------------------------------- 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
