Maciej Swiderski wrote:
Exanle of BPMN2 file you can find here and sample code that operates on this can be found in testIntermediateCatchEventSignal() method here
Thank you.
However it brings more questions then answers :)
Here is the diagram of that process model:
(/jbpm-examples/src/main/resources/junit/BPMN2-IntermediateCatchEventSignal.bpmn2)
https://community.jboss.org/servlet/JiveServlet/downloadImage/2-716976-17983/450-137/jbpm+screenshot+wait+state+examples.png
Why there are two lanes? One process, but two lanes. How they are supposed to influence each other?
Note: The "User Task" is a custom task mapped to DoNothingWorkItemHandler, which does nothing, empty handler, but in the task properties is selected "Wait for Completion = true"
The "event" (beginning of the second "line") is the mentioned intermediateCatchEvent task.
I made a bit modified version of this example:
https://community.jboss.org/servlet/JiveServlet/downloadImage/2-716976-17984/450-104/jbpm+screenshot+wait+state+examples+my+modification.png
When I re-run test now:
When I start the process, "Print something 1" is printed as expected.
When I send signal to the process, the "Print something 3" is printed, as expected.
And there is end of process.
The "Print something 2" is never reached.
More interestingly, the test is evaluated as "completed" even, despite the process still did not finished the "first line".
Puzzling I have to say.
Yes, I have my wait state, but still no idea how to signalize it to move to the next task.
