For shared Tuscany runtime for webapp, the extension point registry is shared as most of the extension points or extensions are independent of the composite applications. If a system service like the CompositeActivator that keeps states for the application, we create a new instance per Node. If we see the need to have different instances of EndpointRegistry for nodes created by the same NodeFactory, we can do that too.
Thanks, Raymond From: ant elder Sent: Thursday, June 25, 2009 3:53 AM To: [email protected] Subject: Re: Tuscany Tomcat integration On Thu, Jun 25, 2009 at 10:59 AM, Simon Laws <[email protected]> wrote: Can you say something about how the libs in the Tuscany webapp are provided to each of the sca webapps/applications. This would probably work OK if the endpoint registry were shipped with the tomcat hook as it would be in the common classloader. A very specific Tomcat solution and would still need to distribute the registry to include tomcat in a wider domain. Simon When the "Tuscany runtime is shared" box has been ticked then there is a single class loader for all the Tuscany jars and thats added as the parent class loader for all sca contributions and sca enabled webapps. So in that case it doesn't need to go in the tomcat hook as the endpoint registry contents are already shared between all those as it uses static for the endpoints and endpointreferences fields. (In fact, they don't need to be statics because now that all the Node runtime stuff is moved to the NodeFactory and the NodeFactory newInstance isn't actually returning a new instance but a shared instance so there is only a single instance of the tuscany runtime and only a single EndpointRegistry instance. Not actually sure if that is the intention, and its doesn't look like it works if multiple nodes try to use different configurations in the one JVM) ...ant
