Thanks, I am using the setsession to make this integration work. like jbpmContext = jbpmConfiguration.createJbpmContext(); jbpmContext.setSession(<>);
Now the session object is handling all the database activities for me. The session is getting opened and also closed automatically by my transaction manager configured thru spring. I may need some info for the scenario below: Actual problem now when i try to close the context using jbpmContext.close() jbpm tries to close the session associated with the context. as the session was automatically closed when i moved out of my method and trying to close the jbpmconext later after doing some business logic. couple of ways i have in my mind,but not sure if this si right. 1) should we close the jbpm context after every action we do and create a new one later,will it not affect the performance. 2) Should we not close the jbpmconext in this scenario, Will there be any problems in keeping the context's in the stack which are of no use. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155441#4155441 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155441 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
