commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rahul Akolkar (JIRA)" <>
Subject [jira] Commented: (SCXML-105) Current status updated after onentry is called
Date Sun, 11 Jan 2009 18:35:59 GMT


Rahul Akolkar commented on SCXML-105:

Thanks for your patches and suggestions. In the spirit of the latest suggestion, more changes
would be needed though. During a transition, you'd be in neither the source nor target states
(however, theoretically transitions are supposed to be instantaneous so state chart theory
doesn't need to address that very much). So it'd look something like:

// here status returns source(s) as current states
// here status returns no current states (which is quite bad IMO)
// here status returns target(s) as current states

I will try to clarify with the Working Group what the consensus is regarding the behavior
here, but I'd be inclined to not make any changes until such time.

> Current status updated after onentry is called
> ----------------------------------------------
>                 Key: SCXML-105
>                 URL:
>             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,
> 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.

View raw message