You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Rahul Akolkar (JIRA)" <ji...@apache.org> on 2007/08/06 23:39:59 UTC
[jira] Resolved: (SCXML-49) SimpleSCXMLInvoker may miss transition
to final state
[ https://issues.apache.org/jira/browse/SCXML-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rahul Akolkar resolved SCXML-49.
--------------------------------
Resolution: Fixed
Fixed in trunk. Thanks for the test case.
> SimpleSCXMLInvoker may miss transition to final state
> -----------------------------------------------------
>
> Key: SCXML-49
> URL: https://issues.apache.org/jira/browse/SCXML-49
> Project: Commons SCXML
> Issue Type: Bug
> Affects Versions: 0.6
> Reporter: Ingmar Kliche
> Assignee: Rahul Akolkar
> Fix For: 0.7
>
>
> The current implementation of SimpleSCXMLInvoker assumes that only external events, handled by parentEvents(), may cause the child state machine to go move a final state. But in case where the invoked state machine moves to a final state directly (while executing the initial state, see example) the parent never receives an "invoke.done".
>
> <scxml xmlns=http://www.w3.org/2005/07/scxml version="1.0" initialstate="state1">
> <state id="state1">
> <onentry>
> <send event="foo"/>
> </onentry>
> <transition event="foo" target="state2" />
> </state>
>
> <state id="state2" final="true" />
> </scxml>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.