While it is true that you can put Tapestry library in the shared classloader (I do it in the development environment) and you can share the registry, you still can't call from one webapp into another, as the services themselves will still be loaded by different classloaders and cannot be shared.
On Dec 14, 2012, at 3:31 AM, Lance Java wrote: >> You cannot use approach #2. Two separate web apps cannot call each other > directly. >> This is like having two processes on separate machines in separate JVMs. > > This is not entirely true. As Josh said there is a classloader which is > common to all webapps running in a container. Take a look at the classloader > hierarchy here: > http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html. > > I agree with Josh that if you put your jars in the shared lib folder > (instead of mywebapp/WEB-INF/lib) you might be able to share the registry. > I'm just not sure if it's a good idea ;) > > > > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Sharing-the-Registry-instance-between-web-applications-deployed-in-the-same-container-tp5718686p5718716.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
