On Thu, Jun 4, 2009 at 4:47 PM, Raymond Feng <[email protected]> wrote: > 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.
I agree. Was just checking there wasn't some deeper thinking behind it. Just putting some changes in now to make the "in JVM" endpoint registry work. Looking through the code today I notice other changes so that the organization now seems to be.... N X NodeFactory (1 per JVM) | N X Node (all nodes within a JVM share a factory) Is this just to allow nodes to share the loaded extensions? Simon
