User development,
A new message was posted in the thread "Question About Forks and Modeling Rework
Requests in jbpm4":
http://community.jboss.org/message/531761#531761
Author : Robert Moskal
Profile :
http://community.jboss.org/people/rmoskal
Message:
--------------------------------------------------------------
I've done a bit more research on this forking behavior and decided to test against the
4.4 snap-shot as well as against 4.1. Mainly to see whats' changed. I simplified my
process definition a little:
http://community.jboss.org/servlet/JiveServlet/downloadImage/2329/Screens...
I thought I would implement the use case that would work for my client. When we get to
*state2* and *state3* and we signal *state2* to return to *state1*, we would simply end
the *state3* execution. When I did this under 4.4 some unexpected things happened, but
some mysteries were cleared up from 4.1. The entire test case is attached (in case anyone
wants to experiment), but the important part is here:
//Lets' end the bottom execution
ExecutionImpl bottomPath = (ExecutionImpl)
processInstance.findActiveExecutionIn("state3");
bottomPath.end();
assertTrue(bottomPath.isEnded());
--------------------------------------------------------------
To reply to this message visit the message page:
http://community.jboss.org/message/531761#531761