[
https://issues.apache.org/jira/browse/TUSCANY-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignacio Silva-Lepe closed TUSCANY-706.
--------------------------------------
Resolution: Fixed
> Revised approach for callback invocation chains, callback correlation and
> routing
> ---------------------------------------------------------------------------------
>
> Key: TUSCANY-706
> URL: https://issues.apache.org/jira/browse/TUSCANY-706
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Core
> Affects Versions: Java-Mx
> Reporter: Ignacio Silva-Lepe
> Assigned To: Ignacio Silva-Lepe
> Fix For: Java-Mx
>
> Attachments: RevisedCallbackChainsCorrelationAndRouting.patch,
> RevisedCallbackChainsCorrelationAndRouting.patch
>
>
> A revised approach is provided for callback invocation chains. Source
> callback chains, which used to be located in outbound wires, are now located
> in inbound wires. In addition, since more than one outbound wire can be
> connected to an inbound wire, it is necessary to maintain one source callback
> chain per operation per target outbound wire. This is maintained by an
> inbound wire in a table keyed by outbound wire container 'address' (currently
> SCAObject name).
> In addition, correlation and routing of callback messages needs to take into
> account this revised callback chain approach. As a starting approach, a
> routing table is maintained by an inbound wire that maps message ids to
> target outbound wire container addresses. A forward message carries with it a
> message id that becomes the corresponding callback message's correlation id.
> This allows a callback message to be correlated with the source callback
> chain whose target outbound wire originated the forward message.
> The attached patch implements the revised callback invocation chain approach,
> callback correlation and routing. It passes all core test cases and the
> simple callback sample. In addition, it was necessary to make a couple of
> changes to the groovy container. The patch passes all groovy test cases, but
> more extensive testing of the groovy container may be appropriate.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
