[
https://issues.apache.org/jira/browse/SCXML-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662705#action_12662705
]
Mike Tillberg commented on SCXML-105:
-------------------------------------
The additional updateStatus call may not be the correct fix. When that is in
place, getting the state in an onExit or in a transition returns the
destination state. It looks like this may be a deeper problem.
SCXMLSemantics.executeActions is defined to execute "all
OnExit/Transition/OnEntry transitional actions", which would infer that the
same state would be current for all of those sections.
> 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: 0.10
>
> Attachments: custom-state-01.xml, CustomActionTest.patch,
> GetStateAction.java
>
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
