[jboss-dev-forums] [Design of JBoss jBPM] - Re: Can't deploy processdefinition from GPD into jBPM 3.2 -

anonymous wrote : 3.8.3. Current Session context management with JTA | | The easiest way to handle Sessions and transactions is Hibernates automatic "current" Session management. See the discussion of Section 2.5, ?Contextual Sessions?. Using the "jta" session context, if there is no Hibernate Session associated with the current JTA transaction, one will be started and associated with that JTA transaction the first time you call sessionFactory.getCurrentSession(). The Sessions retrieved via getCurrentSession() in "jta" context will be set to automatically flush before the transaction completes, close after the transaction completes, and aggressively release JDBC connections after each statement. This allows the Sessions to be managed by the lifecycle of the JTA transaction to which it is associated, keeping user code clean of such management concerns. Your code can either use JTA programmatically through UserTransaction, or (recommended for portable code) use the Hibernate Transaction API to set transaction boundaries. If you run in an EJB container, declarative transaction demarcation with CMT is preferred. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4003170#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...