Hi,
We creating an application n structs and hibernate and we also using jbpm as a workflow engine i have a query.
I've created a workflow process, but I'm unable to proceed further.
Requirement:
1) Run Two Parallel Tasks
2)In Both sides means LHS and RHS I have a couple of nodes before join them. but flow got stuck to first node of both LHS and RHS.... for solving this I have used Super state so my problem is solved now in LHS flow is moving to next flow but now it won't able to initiate RHS flow.
Please help me to resolve my issue.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4265674#4265674
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4265674
Well, I was not aware that you were using JPA.
You should not be using "hibernate-configuration" in jbpm.cfg.xml file when using SpringConficuration.
If you use JPA then you need to mention the mapping locations in persistance.xml of JPA. Whatever you mentioned in your TODO list, of moving things to persistance.xml should do the work for you.
And also do not create the session factory bean if you are using JPA. That is only valid for hibernate-spring combination.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4265650#4265650
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4265650
Actually your assumption that the first user who executes step 3 wins is not always correct. May be most of the time it happens that way for your case.
It has to be that the first of the two treads which does a hibernateSession.flush() will win. This is a desired behaviour from hibernate, and this is a very important feature.
I think the solution you thought of catching StaleObjectStateException is fair enough. Make sure that your "try" boundary is the smallest possible so that you do not catch StaleObjectStateException happening because of some other reason.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4265649#4265649
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4265649
org.jbpm.jpdl.internal.xml.JpdlParser is the cental class which does the parsing. And there are binding classes which parse the individual nodes. For example, there is "org.jbpm.jpdl.internal.activity.StartBinding" for parsing start node. You will see the full list in jbpm.jpdl.bindings.xml.
Once you generate the xml, you typically should not need to parse it by calling JpdlParser, NewDeployment.deploy() method does it all for you.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4265648#4265648
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4265648