[TUSCANY-1909] Conversational Component referring to another Conversational Component always uses the same instance

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Java-SCA-1.1
• Component/s: SCA Java Runtime
• Assignee: Simon Nash
• Reporter: Mark Combellack
• Created: 13/Nov/07 19:37
• Updated: 18/Sep/10 11:30
• Resolved: 18/Nov/07 23:55

Description

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.