Hi Hough, Unfortunately, there isn't any documentation on this (Container Managed Persistence w/ jBPM 5) that I know of. I've asked around a little and couldn't find any. What are you using transactions for in your case? jBPM itself has some mechanisms that manage transactions. Regards, Marco houghvw wrote: -- View this message in context: http://drools.46999.n3.nabble.com/Using-JBPM-5-with-Container-Managed-Per... Sent from the Drools: User forum mailing list archive at Nabble.com.

Hi, Container Managed Persistence refers to Entity Beans, and there are no Entity Beans anymore in EJB3. So I assume you're refering to Container Managed Transactions. The transaction needs to be started after the StatefulKnowledgeSession has been created; so with CMT you would need to create the session before the EJB is called. But since the EJB itself is creating the session, I can think of no standard way to do that as of JavaEE 6. Even an interceptor should be called after the transaction has begun with CMT. Probably the easiest for you would be to create an EJB3 interceptor that deals with the boilerplate (creates/disposes the session and starts/commits/rolls back the transaction). Hope this helps, Nick On 11-08-17 09:02 AM, houghvw wrote: