commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ate Douma (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (SCXML-264) Support <invoke> with inline (<content> body) SCXML statemachine definition
Date Sun, 10 Dec 2017 15:26:00 GMT

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

Ate Douma closed SCXML-264.
---------------------------
    Resolution: Fixed

Fixing 24 more SCXML IRP tests, only 16 for jexl datamodel and 22 for ecmascript datamodel
tests remaining to fix!

> Support <invoke> with inline (<content> body) SCXML statemachine definition
> ---------------------------------------------------------------------------
>
>                 Key: SCXML-264
>                 URL: https://issues.apache.org/jira/browse/SCXML-264
>             Project: Commons SCXML
>          Issue Type: New Feature
>            Reporter: Ate Douma
>            Assignee: Ate Douma
>             Fix For: 2.0
>
>
> The SCXML [Invoke|https://www.w3.org/TR/2015/REC-scxml-20150901/#invoke] allows specifying
the target process (another SCXML statemachine) to be defined 'inline' through a child <content>
element.
> The <content> element itself can either use a src expression (to load the SCXML
from data) or inline body.
> To support this feature the Invoker, which currently only loads another SCXML statemachine
from an external resource (remote url or file path) also need to be able to parse a statemachine
definition directly inline.
> Because the SCXMLReader currently cannot parse XML directly, the embedded statemachine
definition (XML fragment) first will be transformed back into a string, so the Invoker can
use the SCXMLReader to parse a new SCXML instance.
> Embedded SCXML with the <invoke> is a common and most convenient usage, and implementing
this feature will fix 24 more SCXML IRP tests!



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message