Indeed, keeping the context open for several transactions does not seem to work
at all. It's a pity.
But I continued my experiments and found that it seems not to be very bad to
save a ProcessInstance to another JbpmContext than it was loaded from.
So, for the moment, my workaround is to load ProcessInstances not forUpdate. In
the action method which successfully ends the conversation, I open a new
JbpmContext, save the ProcessInstance to that context and flush the hibernate
session:
| @End
| public String actionButton() {
| JbpmContext ctx =
| JbpmConfiguration.getInstance().createJbpmContext();
| try {
| ctx.setSession(session);
| ctx.save(processInstance);
| } finally {
| ctx.close();
| }
| session.flush();
| return "startseite";
| }
|
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104423#4104423
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104423
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
