commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rahul Akolkar (JIRA)" <>
Subject [jira] Updated: (SCXML-110) Adjust TriggerEvent according to SCXML Working Draft (7 May 2009)
Date Tue, 14 Jul 2009 17:33:14 GMT


Rahul Akolkar updated SCXML-110:

    Fix Version/s: 1.0

Yup, this needs to be done. Before you get into details, may be useful to look at SCXML-108
-- there seem to be some changes in that patch to address this partly atleast. I haven't looked
at those portions (regarding _event) from the patch in detail but we'd want to use any work
that already has been done if its suitable. Note that part of SCXML-108 (particularly, the
Rhino support has been added to the J6 branch in SVN, but no to trunk yet).

Setting fix version(s) to next release.

> Adjust TriggerEvent according to SCXML Working Draft (7 May 2009)
> -----------------------------------------------------------------
>                 Key: SCXML-110
>                 URL:
>             Project: Commons SCXML
>          Issue Type: Task
>            Reporter: Ales Dolecek
>             Fix For: 0.10, 1.0
> The standard now mandate that:
> a) _event variable exists while processing transitions triggered by event
> b) the _event has following properties: name, type, sendid, origin, origintype, invokeid
and data
> I belive that following changes are needed:
> a) create internal "context wrappers" that will be used inside SCXMLExecutor#triggerEvents
>   - JEXL nor EL does not allow identifiers starting with _
> b) the TriggerEvent should be chaged or replaced to supprot the attributes above

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message