On Thu, Jun 25, 2009 at 11:53 AM, ant elder<[email protected]> wrote: > > > 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 > >
And is does work when the runtime is shared. It doesn't though when the runtime is not shared. I was referring to the non-shared case when I was asking about the classloaders and libs. Or are you saying that you don't think we should support the non-shared case? Simon
