Since you have a transition from task3 to the join, it is in the incoming
transitions and the join expects an incomming token/execution. It cannot easily
decide there will not be a token comming from task3.
Two things come to mind:
- implement your own join node
- use the n-out-of-m
thanx for ur quick reply.
The second option (multiplicity attribute) may not work for me :(
coz, number of transitions may vary as per my requirment.(0 to 7 and more)
Option 1 - suits better for me. I've changed the JoinActivity of JBPM Source
code and its working. But it should not be like
