[
https://jira.jboss.org/jira/browse/JBPM-642?page=com.atlassian.jira.plugi...
]
Alejandro Guizar updated JBPM-642:
----------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Committed a trivial solution to this issue: to lock the parent token parked in a fork
node. Later on, the join node unlocks the parent token before it leaves.
This solution does not hide the parent token from the application, but does prevent
signals from reaching the parent token and making a mess out of the process instance.
Signaling RootToken on Fork Node
---------------------------------
Key: JBPM-642
URL:
https://jira.jboss.org/jira/browse/JBPM-642
Project: jBPM
Issue Type: Feature Request
Components: Runtime Engine
Affects Versions: jBPM 3.2.9
Reporter: Enric Cecilla
Assignee: Alejandro Guizar
Fix For: jBPM 3.2.x
Attachments: mylyn-context.zip
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Giving the following processdefinition:
*start->fork->a->join->end
->b ^
When RootToken is on Fork node trying to signal again the RootToken actually moves the
token to one branch state, then RootToken can be signalled til it is on the Join node. At
that moment it can be signalled again and it leaves the Join node.
pi.signal();
assertEquals( "fork", pi.getRootToken().getNode().getName() ); //true
pi.signal();
assertEquals( "b", pi.getRootToken().getNode().getName() ); //true
pi.signal();
assertEquals( "join", pi.getRootToken().getNode().getName() ); //true
Does it makes any sense being able to signal a RootToken on Fork node which has children
on every branch? From my point of view signalling on that condition should throw and
Exception. Only child tokens should be allowed to signal since "real" tasks are
on child tokens
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira