commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Woonsan Ko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SCXML-100) Support _event variable
Date Thu, 02 Jan 2014 20:21:50 GMT

    [ https://issues.apache.org/jira/browse/SCXML-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13860713#comment-13860713
] 

Woonsan Ko commented on SCXML-100:
----------------------------------

Translated TriggerEvent.ERROR_EVENT and TriggerEvent.CHANGE_EVENT into 'platform' type event
variables, and all the others into 'external' type event variables based on the spec 5.10.1.

By the way, because the current Send model for <send> element doesn't support any target
attribute values yet, we can't support 'internal' event variables either. Also, if we want
to support determination of 'sendid', 'origin' and 'origintype' based on the context, we need
to refactor many parts.
So, I'll create a separate issue for the refactoring for the future release (2.1 or later)
and resolve this issue.

> 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.5#6160)

Mime
View raw message