See my comments inline.

--------------------------------------------------
From: "Simon Laws" <[email protected]>
Sent: Thursday, June 04, 2009 9:52 AM
To: <[email protected]>
Subject: Re: [2.x] change in behaviour for contribution loading

[[snip]]
Looking through the code today I notice other changes so that the
organization now seems to be....

N X NodeFactory (1 per JVM)

NodeFactory.newInstance() will return the same instance. It can more than one instances in the same JVM too when the NodeFactory is loaded by different classloaders. For example, it is the case when we package all Tuscany jars in the webapp.

|
N X Node (all nodes within a JVM share a factory)

Is this just to allow nodes to share the loaded extensions?

Yes, the same NodeFactory will share the same extension point registry. Almost all of the extensions and extension points are independent of the application composites. It's much performed to share, especially in the managed environment such as OSGi or Web/JEE. The only utility that contains application information is the CompositeActivator. We get a new instance for each node.


Simon

Reply via email to