Calling EmbeddedSCADomain.activateDomain() after adding a contribution renders
services from previous contribution unusable
----------------------------------------------------------------------------------------------------------------------------
Key: TUSCANY-1480
URL: https://issues.apache.org/jira/browse/TUSCANY-1480
Project: Tuscany
Issue Type: Bug
Affects Versions: Java-SCA-0.91
Reporter: Vamsavardhana Reddy
Here is a situation I am running into.
Step 0: Create an EmbeddedSCADomain.
Step 1: Add contribution from contribution1.jar (which provides say
"Service1") to EmbeddedSCADomain from Step 0.
Step 2: Call EmbeddedSCADomain.DomainCompositeHelper.activateDomain()
Step 3: Call EmbeddedSCADomain.DomainCompositeHelper.startComponent() on all
componets from contribution1.jar.
Step 4: Add contribution from contribution2.jar (which provides say
"Service2") to EmbeddedSCADomain from Step 0.
Step 5: Call EmbeddedSCADomain.DomainCompositeHelper.activateDomain()
Step 6: Call EmbeddedSCADomain.DomainCompositeHelper.startComponent() on all
componets from contribution2.jar.
After Step 3, I am able to run Service1 successfully. At Step 5, I get a
message like the following:
"Composite assembly problem: Service not found for component service:
CalculatorServiceComponent/$promoted$.CalculatorService"
After Step 6, Service1 no longer runs, where as Service2 runs successfully.
If I call DomainCompositeHelper.startComponent() on each of the components
from the first contribution after deploying the second, (that is after Step
6 from), it results in an Exception which I ignore and continue. But
towards the end I have services from both contributions running
successfully.
--
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]
