[jira] [Resolved] (SCXML-162) internal transition in compound state implementation - SCXML spec

["Ate Douma (JIRA)" <ji...@apache.org>]

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

Ate Douma resolved SCXML-162.
-----------------------------

    Resolution: Fixed

This has been implemented now through SCXML-196

> internal transition in compound state implementation - SCXML spec
> -----------------------------------------------------------------
>
>                 Key: SCXML-162
>                 URL: https://issues.apache.org/jira/browse/SCXML-162
>             Project: Commons SCXML
>          Issue Type: Improvement
>    Affects Versions: 0.9
>            Reporter: vance huang
>            Priority: Minor
>             Fix For: 2.0
>
>
> According to the SCXML spec, the following was stated:
> "The behavior of transitions with 'type' of "internal" is identical, except in 
> the case of a transition whose source state is a compound state and whose 
> target(s) is a descendant of the source. In such a case, an internal transition 
> will not exit and re-enter its source state, while an external one will, as 
> shown in the example below."
> <state id="s1" initial="s11">       
>   <onentry>         
>      <log expr="entering S1"/>
>   </onentry>
>   <onexit>
>      <log expr="'leaving s1'"/>
>   </onexit>
>   <state id="s11">
>      <onentry>
>         <log expr="entering s11"/>
>      </onentry>
>      <onexit>
>         <log expr="'leaving s11'"/>
>      </onexit>
>   </state> 
>   <state id="s12">
>      <onentry>
>         <log expr="entering s12"/>
>      </onentry>
>      <onexit>
>         <log expr="'leaving s12'"/>     
>      </onexit>
>   </state>
>   <transition event="e" target="s12" type="internal">
>      <log expr="'executing transition'"/>      
>   </transition>
> </state>
> Assuming we are in s11 when event e fired. The SM should not go out of s1 and enters s12. 
> This feature needs to be implemented. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)