commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rahul Akolkar (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (SCXML-57) Parallel exits to soon.
Date Sun, 02 Sep 2007 19:57:19 GMT

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

Rahul Akolkar resolved SCXML-57.
--------------------------------

    Resolution: Invalid

Your understanding of the semantics of <parallel> is correct. However, you have missed
a detail in the test case.

The state with ID "thirty_one" has the following transition:

  <transition event="thirty_one.done" target="forty"/>

Reaching a final substate of this state causes the .done derived event above to be triggered,
and the transition above to be followed (which requires us to exit the <parallel>).

Please feel free to ask any further questions on the mailing list.



> Parallel exits to soon.
> -----------------------
>
>                 Key: SCXML-57
>                 URL: https://issues.apache.org/jira/browse/SCXML-57
>             Project: Commons SCXML
>          Issue Type: Bug
>    Affects Versions: 0.6, 0.7
>         Environment: windows and linux 
>            Reporter: Dennis Cook
>         Attachments: transitions-01.xml, Transitions01Test.java
>
>
> I am not sure if this is a bug or the intended behaviour, but it seems that the any one
of the states in the parallel reaches a final substate, then all of parallel states are exited.
 I confirmed this by expanding on the existing test case that uses the transitions-01.xml
state chart to mark one of the three substates with the final="true" attribute.  When this
substate is reached all three of the parallel states are exited.
>  
> However when reading the working draft specification it states:
>  
> Parallel is a wrapper element that encapsulates a set of parallel states. The <parallel>
element has <onentry> and <onexit> elements analogous to <state>. In addition,
the <parallel> element holds a set of <state> elements that execute in parallel
and join at the <onexit> handler of the <parallel> element. In particular, when
all of the parallel substates reach final states, a completion event "ID.done" is generated,
where "ID" is the "id" of the <parallel> element. Either the <parallel> element
or one of its ancestors can trigger a transition off this event, at which time the <onexit>
handler of the element will be executed.
>  
> This leads me to believe that all states of the parallel have to reach a final state
before the tranistion out occurs.  
>  
> Feels like a bug to me.

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


Mime
View raw message