IIRC, we used to support only one deployable composite in 2.x. When I
updated the NodeImpl with NodeConfiguration, I added the code to build all
the deployable composites and activate them.
I think we should use the EndpointRegistry to resolve this issue
consistently for the cases listed below:
1) A node with multiple deployable composites
2) A JVM with multiple nodes
3) Multiple JVMs that host multiple nodes
1 & 2 can be fixed with a JVM scoped EndpointRegistry.
Thanks,
Raymond
--------------------------------------------------
From: "Simon Laws" <[email protected]>
Sent: Thursday, June 04, 2009 1:45 AM
To: "tuscany-dev" <[email protected]>
Subject: [2.x] change in behaviour for contribution loading
If I create a node as follows
node = factory.createNode(new Contribution("client",
"..\\helloworld-client\\target\\itest-nodes-helloworld-client-2.0-SNAPSHOT.jar"),
new
Contribution("service",
"..\\helloworld-service\\target\\itest-nodes-helloworld-service-2.0-SNAPSHOT.jar"));
Where the client contribution has a service that references a
component in the service contribution
I get a "WARNING: Component reference target not found" because the
code builds each deployable composite separately as opposed to
building the domain as a whole. This is not the case in 1.x where this
scenario will work. Our endpoint registry will have the effect of
fixing this but I'm wondering whether it's like this at the moment
because...
1/ changes were made to 1.x but not 2.x
2/ someone decided that building the domain composite in a node is the
wrong thing to do for some reason.
I suspect the answer is 1/ but I'm just checking.
Simon
