[
https://issues.apache.org/jira/browse/TUSCANY-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567599#action_12567599
]
Thomas Greenwood commented on TUSCANY-2035:
-------------------------------------------
My colleagues have created a patch for this, but it's a bit rough and has some
issues. We could try and attach a patch file if you think it might help.
We were thinking that it this change was made then it might be possible to
start thinking about removing the ThreadMessageContext thread local. This
would make it easier for people to use threading in Tuscany.
> Injected callback references are not resolved at the time of injection
> ----------------------------------------------------------------------
>
> Key: TUSCANY-2035
> URL: https://issues.apache.org/jira/browse/TUSCANY-2035
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core Runtime
> Affects Versions: Java-SCA-1.1
> Environment: All
> Reporter: Simon Nash
> Assignee: Simon Nash
> Fix For: Java-SCA-Next
>
>
> When a callback reference is injected as a proxy or a CallableReference, the
> callback target should be resolved at the time of injection to the caller's
> callback service or the target of any ServiceReference provided by a
> setCallbackObject() call. Tuscany currently does not do this, but resolves
> the callback target as the time of use, relative to the current invocation
> context at that time. For example, if A invokes B and C subsequently invokes
> the same B instance, any callbacks from the C invocation through references
> that were injected by the A invocation will go to C instead of going to A as
> they should.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
