commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ate Douma (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SCXML-105) Current status updated after onentry is called
Date Thu, 03 Apr 2014 09:27:15 GMT

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

Ate Douma resolved SCXML-105.
-----------------------------

    Resolution: Not a Problem

Indeed, with SCXML-196 the processing logic and order is now exactly according to the specification,
so closing this as 'Not a Problem' (any more).

> Current status updated after onentry is called
> ----------------------------------------------
>
>                 Key: SCXML-105
>                 URL: https://issues.apache.org/jira/browse/SCXML-105
>             Project: Commons SCXML
>          Issue Type: Bug
>    Affects Versions: 0.9
>            Reporter: Mike Tillberg
>            Priority: Minor
>             Fix For: 2.0
>
>         Attachments: CustomActionTest.patch, GetStateAction.java, custom-state-01.xml
>
>
> When retrieving the current state using a custom action in the onentry section of a state,
the state is incorrect.  The state retrieved is the previous state.  The problem appears to
be in SCXMLExecutor.triggerEvents, where updateStatus() is called after semantics.executeActions().
 Adding an additional updateStatus() before executeActions() seems to fix the problem, and
all tests still pass.
> Attached is a test case showing the problem.



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

Mime
View raw message