[
https://issues.apache.org/jira/browse/SCXML-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13829478#comment-13829478
]
Woonsan Ko edited comment on SCXML-100 at 11/21/13 11:42 PM:
-------------------------------------------------------------
Just for the record, since 20080516 [1], _eventdata seems to have been replaced
by _event variable.
For scxml document compatibility, I think SCXMLExecutor set both _event and
_eventdata, and possibly it can log warning on accesses to the deprecated
_eventdata access.
And let's deal with the readonly system variable support separately in SCXML-99.
[1] http://www.w3.org/TR/2008/WD-scxml-20080516/#SystemVariables
was (Author: woon_san):
Just for the record, since 20080516 [1], _eventdata seems to have been replaced
by _event variable.
For scxml document compatibility, I think SCXMLExecutor set both _event and
_eventdata, and possibly it can log warning on accesses to the deprecated
_eventdata access.
[1] http://www.w3.org/TR/2008/WD-scxml-20080516/#SystemVariables
> 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 was sent by Atlassian JIRA
(v6.1#6144)
