[jira] Updated: (SCXML-36) Invoke cancel method called despite special done event triggered

["Rahul Akolkar (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SCXML-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rahul Akolkar updated SCXML-36:
-------------------------------

    Fix Version/s: 0.7

Lets see if the next draft sheds some light on this, setting fix version to next release (0.7) for now.


> Invoke cancel method called despite special done event triggered
> ----------------------------------------------------------------
>
>                 Key: SCXML-36
>                 URL: https://issues.apache.org/jira/browse/SCXML-36
>             Project: Commons SCXML
>          Issue Type: Bug
>    Affects Versions: 0.6
>            Reporter: Elam Birnbaum
>            Priority: Minor
>             Fix For: 0.7
>
>
> Creating an invoker class by implementing the Invoker interface requires you to implement the invoke, parentEvents, and cancel methods. The invoke method is expected to perform the invoker's task and the user must trigger a special done event within it to signify the invoker is complete. The cancel method is expected to be called from the outside to cancel the invoke process, especially if the invoke process were being handled in a separate thread and the thread has become a zombie. It would be called if an event were triggered while the state engine was within the state containing the invoke, since that event would be expected to interrupt the invoke. The issue, however, is that the cancel method is called even if the triggered event is the special done event signifying the end of the invoke, causing the cancel method to always be called regardless of whether the invoke was indeed a zombie or not.
> The system should work so that the special done event triggered while in an invoke should not cause the cancel method on the invoker class to be called. An investigation should take place to determine if this should apply to any event triggered by the invoker itself (though I am not sure how you are able to make that determination if the invoker spawns off separate threads that could trigger the events) should cause the cancel method to be called.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org