There has been an email discussion about jBPM's JTA integration. anonymous wrote : I am referring to the fact that Hibernate needs to be flushed in beforeCompletion(), and closed in afterCompletion(), which is currently impossible because everything happens in the close() method. | ________________________________ | | From: Tom Baeyens | Sent: Thursday, December 14, 2006 5:05 AM | To: Gavin King | Cc: Dev - jBPM | Subject: RE: jBPM *still* unusable in JTA environment | | we have fixed this in head, but it is not yet backported to 3.1 branch. | | at least, if you are referring to the capability of using the hibernate current session. | ________________________________ | | From: Gavin King | Sent: Thu 12/14/2006 6:25 AM | To: Dev - jBPM | Subject: jBPM *still* unusable in JTA environment | | Guys, when are we going to get this fixed? It's been a long time since I raised this really major issue. I now have added a configuration property to jBPM 3.1 to get this behaviour: a) when a jbpm needs a hibernate session, it uses SessionFactory.getCurrentSession() b) at jbpmContext.close(), jbpm does not do anything with the hibernate session. no flush and no close. Do you need the flush method to be exposed too ? Eventually i want to add it, but doing that in 3.1.x might be tricky. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995305#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...