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] [Updated] (SCXML-259) Complete implementation and handling of system variables _event and _ioprocessors
Date Sun, 10 Dec 2017 03:02:00 GMT

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

Ate Douma updated SCXML-259:
----------------------------
    Description: 
The SCXML [System Variables|https://www.w3.org/TR/2015/REC-scxml-20150901/#SystemVariables]
_event was only minimally implemented so far.

The _event.sendid, _event.origin, _event.origintype, _event.invokeid all need to be set and
handled accordingly to the external communication requirements, including their proper error
handling and feedback/return values from an invoked process.

The SCXML [Event I/O Processors|https://www.w3.org/TR/2015/REC-scxml-20150901/#eventioprocessors]
implementation and handling was also not complete yet.
Besides completing the handling of the #_internal, #_parent and #_invokeid processors, also
the 'location' field for the standard CXMLEventProcessor needs to be made available.

To support the extended _event variable handling a new EventBuilder class will be introduced,
which can/should be used to build a TriggerEvent instead of instantiating these directly.
Furthermore to align with the specification naming, the TriggerEvent#payload field and getter
method will be renamed to #data (getData()).

Finally, this also requires better, and fixed, handling of the management and communication
(bi-directionally) with the Invoker and the statemachine invoked.
As result the AsyncTrigger class no longer is (nor can be) used and will be dropped.

Alltogether this will fix another 12+ W3C SCXML IRP tests! 

  was:
The SCXML [System Variables|https://www.w3.org/TR/2015/REC-scxml-20150901/#SystemVariables]
_event was only minimally implemented so far.

The _event.sendid, _event.origin, _event.origintype, _event.invokeid all need to be set and
handled accordingly to the external communication requirements, including their proper error
handling and feedback/return values from an invoked process.

The SCXML [Event I/O Processors|https://www.w3.org/TR/2015/REC-scxml-20150901/#eventioprocessors]
implementation and handling was also not complete yet.
Besides completing the handling of the #_internal, #_parent and #_invokeid processors, also
the 'location' field for the standard CXMLEventProcessor needs to be made available.

To support the extended _event variable handling a new EventBuilder class will be introduced,
which can/should be used to build a TriggerEvent instead of instantiating these directly.
Furthermore to align with the specification naming, the TriggerEvent#payload field and getter
method will be renamed to #data (getData()).

Finally, this also requires better, and fixed, handling of the management and communication
(bi-directionally) with the Invoker and the statemachine invoked.
As result the AsyncTrigger class no longer is (nor can be) used and will be dropped.

Alltogether this will fix another 12+ W3C SCXML IRP tests! 


> Complete implementation and handling of system variables _event and _ioprocessors
> ---------------------------------------------------------------------------------
>
>                 Key: SCXML-259
>                 URL: https://issues.apache.org/jira/browse/SCXML-259
>             Project: Commons SCXML
>          Issue Type: New Feature
>            Reporter: Ate Douma
>            Assignee: Ate Douma
>             Fix For: 2.0
>
>
> The SCXML [System Variables|https://www.w3.org/TR/2015/REC-scxml-20150901/#SystemVariables]
_event was only minimally implemented so far.
> The _event.sendid, _event.origin, _event.origintype, _event.invokeid all need to be set
and handled accordingly to the external communication requirements, including their proper
error handling and feedback/return values from an invoked process.
> The SCXML [Event I/O Processors|https://www.w3.org/TR/2015/REC-scxml-20150901/#eventioprocessors]
implementation and handling was also not complete yet.
> Besides completing the handling of the #_internal, #_parent and #_invokeid processors,
also the 'location' field for the standard CXMLEventProcessor needs to be made available.
> To support the extended _event variable handling a new EventBuilder class will be introduced,
which can/should be used to build a TriggerEvent instead of instantiating these directly.
> Furthermore to align with the specification naming, the TriggerEvent#payload field and
getter method will be renamed to #data (getData()).
> Finally, this also requires better, and fixed, handling of the management and communication
(bi-directionally) with the Invoker and the statemachine invoked.
> As result the AsyncTrigger class no longer is (nor can be) used and will be dropped.
> Alltogether this will fix another 12+ W3C SCXML IRP tests! 



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

Mime
View raw message