You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Ate Douma (JIRA)" <ji...@apache.org> on 2017/12/09 22:53:01 UTC
[jira] [Updated] (SCXML-256) Add SCXMLExecutor.run() ans
SCXMLSemantics.initialize(...) methods and SCXML early/late binding
[ https://issues.apache.org/jira/browse/SCXML-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ate Douma updated SCXML-256:
----------------------------
Summary: Add SCXMLExecutor.run() ans SCXMLSemantics.initialize(...) methods and SCXML early/late binding (was: Add SCXMLExecutor.run() ans SCXMLSemantics.initialize(...) methods and SCXML late binding)
> Add SCXMLExecutor.run() ans SCXMLSemantics.initialize(...) methods and SCXML early/late binding
> -----------------------------------------------------------------------------------------------
>
> Key: SCXML-256
> URL: https://issues.apache.org/jira/browse/SCXML-256
> Project: Commons SCXML
> Issue Type: New Feature
> Reporter: Ate Douma
> Assignee: Ate Douma
> Fix For: 2.0
>
>
> The SCXML specification requires (assumes) that a statemachine runs to completion (final state),
> for which it might need to wait on external events to arrive.
> There also is a requirement for a separate initialize phase in which the statemachine must process and merge (override) root datamodel data passed in from an external invocation (e.g. from an <invoke> execution).
> For the latter feature the SCXMLSemantics interface representing the [ Algorithm for SCXML Interpretation| Algorithm for SCXML Interpretation] will be extended with an additional #initialize(...) method.
> This also requires adding support for SCXML binding="late" or binding="early".
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)