[jbpm-issues] [JBoss JIRA] Commented: (JBPM-642) Signaling RootToken on Fork Node

[JeanDenis Bertron (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBPM-642?page=comments#action_12407204 ] 
            
JeanDenis Bertron commented on JBPM-642:
----------------------------------------

Wow, I'm surprised that almost a year has passed and nothing has been done about this. 
If Forks and Joins don't work as expected -especially according to the documentation - then it's pretty frustrating. 


> Signaling RootToken  on Fork Node
> ---------------------------------
>
>                 Key: JBPM-642
>                 URL: http://jira.jboss.com/jira/browse/JBPM-642
>             Project: JBoss jBPM
>          Issue Type: Feature Request
>          Components: Core Engine
>            Reporter: Enric Cecilla
>         Assigned To: Tom Baeyens
>
> 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: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira