Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Thu, 21 Nov 2013 23:51:36 +0000 (UTC)
From: "Woonsan Ko (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12410413.1228951002328.11501.1385077896019@arcas>
In-Reply-To: <JIRA.12410413.1228951002328@arcas>
References: <JIRA.12410413.1228951002328@arcas>
Subject: [jira] [Updated] (SCXML-100) Support _event variable
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/SCXML-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Woonsan Ko updated SCXML-100:
-----------------------------

    Fix Version/s:     (was: 0.10)
                   2.0

> 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: 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)