[jboss-jira] [JBoss JIRA] Closed: (JBPM-642) Signaling RootToken on Fork Node

[Tom Baeyens (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBPM-642?page=all ]

Tom Baeyens closed JBPM-642.
----------------------------

    Fix Version/s:     (was: jBPM jPDL 3.2.2)
       Resolution: Rejected

i think it makes sense to null out the node pointer in the token after the fork has executed.  in that case it can't be signalled and then it doesn't need another db column.

BUT since i'm not sure of the consequences and people might just rely on the current behaviour, i don't think this feature request is worth while the risk.

So I'm going to bare this in mind for the 4.0 implementation, but in 3.x, we'll leave it as it is now.

> 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