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] [Commented] (SCXML-226) Support of special send targets #_parent and #_invokeid
Date Thu, 12 Feb 2015 01:13:11 GMT

    [ https://issues.apache.org/jira/browse/SCXML-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14317323#comment-14317323
] 

Ate Douma commented on SCXML-226:
---------------------------------

[~hiu.phail] Sorry, can't assign it to you, for that you need higher privileges (which I can't
give you directly right now).

> Support of special send targets #_parent and #_invokeid
> -------------------------------------------------------
>
>                 Key: SCXML-226
>                 URL: https://issues.apache.org/jira/browse/SCXML-226
>             Project: Commons SCXML
>          Issue Type: Bug
>    Affects Versions: 0.5, 0.6, 0.7, 0.8, 0.9
>            Reporter: Michael Goerlich
>            Assignee: Ate Douma
>             Fix For: 2.0
>
>         Attachments: fix_invoke_special_targets
>
>
> Currently it is not possible to use #_parent and #_invokeid to allow communication between
two scxml instances where one invoked the other. 
> Due to the last changes the _ioprocessors variable was introduced. If the target of a
<send> may reference to an entry in the _ioprocessors map, then it should be possible
to forward events directly to the registered SCXMLIOProcessor instance.
> Given this the invoker must supply a SCXMLIOProcessor for the parent to register within
the its SCXMLExecutionContext map as #_invokeId and the invoker must register the parent SCXMLIOProcessor
as #_parent within the execution context of the SCXMLExecutor. As well as this the EventDispatcher
must take the SCXMLIOProcessor registered for the target from _ioprocessors.
> Based on my assumptions I tried to implement this and uploaded the patch to: http://pastebin.com/t855Ugs1
. Hope it helps.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message