Return-Path: 
 <issues-return-46241-apmail-commons-issues-archive=commons.apache.org@commons.apache.org>
X-Original-To: apmail-commons-issues-archive@minotaur.apache.org
Delivered-To: apmail-commons-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 5E1FD172F7
	for <apmail-commons-issues-archive@minotaur.apache.org>;
 Thu, 12 Feb 2015 01:11:12 +0000 (UTC)
Received: (qmail 58831 invoked by uid 500); 12 Feb 2015 01:11:12 -0000
Delivered-To: apmail-commons-issues-archive@commons.apache.org
Received: (qmail 58706 invoked by uid 500); 12 Feb 2015 01:11:12 -0000
Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@commons.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@commons.apache.org>
List-Post: <mailto:issues@commons.apache.org>
List-Id: <issues.commons.apache.org>
Reply-To: issues@commons.apache.org
Delivered-To: mailing list issues@commons.apache.org
Received: (qmail 58694 invoked by uid 99); 12 Feb 2015 01:11:12 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Feb 2015 01:11:12 +0000
Date: Thu, 12 Feb 2015 01:11:12 +0000 (UTC)
From: "Ate Douma (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12774301.1423678648000.20949.1423703472092@Atlassian.JIRA>
In-Reply-To: <JIRA.12774301.1423678648000@Atlassian.JIRA>
References: <JIRA.12774301.1423678648000@Atlassian.JIRA>
 <JIRA.12774301.1423678648404@arcas>
Subject: [jira] [Commented] (SCXML-226) Support of special send targets
 #_parent and #_invokeid
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

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

[~hiu.phail] I've reworked your patch for the remaining #_invokeid support (largely intact) and comitted it.

I don't have a direct test-case available for this yet, but am also working on adding support for embedded scxml <content> in invoke definitions, 
for which the w3c tests have plenty examples including (then) tests for the #_invokeid targets.

But if you can verify if the current changes already work in your context, that would be great!

I leave this issue open and assign it to you for review.
If you have any comments or feedback, please let me know.

Thanks again for the contribution!

p.s. I'm also working on support for the #_scxml_sessionid target, but that needs a little bit more work.
Once I have that working, I'll update and expand this issue (title as well) to add it too.

> 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)