You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Woonsan Ko (JIRA)" <ji...@apache.org> on 2013/12/05 05:28:37 UTC
[jira] [Commented] (SCXML-100) Support _event variable
[ https://issues.apache.org/jira/browse/SCXML-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13839796#comment-13839796 ]
Woonsan Ko commented on SCXML-100:
----------------------------------
Just added '_event' system variable which supports _event.name and _event.data for now. (currently _event.type always returns 'internal' at this moment.)
Still TO-DO: determine type, sendid, origin and origintype based on context
> 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
> Assignee: Woonsan Ko
> Fix For: 2.0
>
>
> 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)