Raymond Feng wrote:
Hi,
I checked in a fix under r629688 by adding a "synchronized" for the
business method. Please confirm if it's meant to test that way.
Thanks,
Raymond
I think the problem is that myServiceCallback is declared as an
instance variable instead of a local variable. I have changed it
to local in r630007 and removed the synchronized block. If this
doesn't fix the problem you were seeing, please let me know.
Simon
----- Original Message ----- From: "Raymond Feng" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, February 20, 2008 7:52 PM
Subject: Re: [jira] Commented: (TUSCANY-2035) Injected callback
references are not resolved at the time of injection
Hi,
I'm seeing random failures in itest-callback-multiple-wires. In this
itest, MyServiceComponent is scoped with "COMPOSITE".
MyClientComponent1 and MyClientComponent2 invokes MyServiceComponent
concurrently. Since the MyServiceComponent is the same instance for
both clients, the requestContext is random (for client1 or client2).
As a result, the callback result is messing up.
Thanks,
Raymond
----- Original Message ----- From: "Simon Nash (JIRA)"
<[email protected]>
To: <[email protected]>
Sent: Monday, February 18, 2008 8:54 AM
Subject: [jira] Commented: (TUSCANY-2035) Injected callback references
are not resolved at the time of injection
[
https://issues.apache.org/jira/browse/TUSCANY-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569946#action_12569946
]
Simon Nash commented on TUSCANY-2035:
-------------------------------------
I've checked in some code under revision 628809 to resolve the
callback target and reference parameters at the time that the
callback reference is created. Could others who have encountered
this issue please try this fix to see what results you are getting?
Thanks.
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
