Conversational Component referring to another Conversational Component always 
uses the same instance
----------------------------------------------------------------------------------------------------

                 Key: TUSCANY-1909
                 URL: https://issues.apache.org/jira/browse/TUSCANY-1909
             Project: Tuscany
          Issue Type: Bug
          Components: Java SCA Core Runtime
            Reporter: Mark Combellack
             Fix For: Java-SCA-Next


I've run into a problem with two conversational Services. Consider the 
following scenario:

AService
  * Has member variable called state
  * Has reference to BService
  * Has set/getState method for setting state on A
  * Has set/getStateOnB method for setting state on B

BService
  * Has member variable called state

Calling SCADomain.getService(AService) twice, I am expecting to get:

     AService_1 -> BService_1
and  AService_2 -> BService_2

However, I am getting:

     AService_1 -> BService_1
and  AService_2 -> BService_1

i.e a second instance of BService is not being created.

The first time I get a new instance of AService, a new instance of BService is 
created.

The second time I get a new instance of AService, the original BService 
instance is shared.


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

Reply via email to