[
https://issues.apache.org/jira/browse/SCXML-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rahul Akolkar updated SCXML-100:
--------------------------------
Affects Version/s: 0.9
Fix Version/s: 0.10
I think deprecating _eventdata until v1.0 (and then removing it) might be a
good way to proceed.
Setting fix version to next release, v0.10.
> Support _event variable
> -----------------------
>
> Key: SCXML-100
> URL: https://issues.apache.org/jira/browse/SCXML-100
> Project: Commons SCXML
> Issue Type: Bug
> Affects Versions: 0.9
> Reporter: Ingmar Kliche
> Fix For: 0.10
>
>
> The SCXML spec defines a variable "_event" which is is bound to a structure
> containing the event name and payload:
> _event.name
> _event.data
> The "_event" variable has to be read-only (from application point of view).
> This change will break backward compatibility of existing SCXML documents.
> Would it be useful to keep the current variable "_eventdata" while adding the
> "_event" structure? "_eventdata" could be marked as depricated and removed
> later.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
