On 1 July 2011 09:58, Ioannis Canellos <[email protected]> wrote: > My comment about being skeptic about Tomcat received a lot of comments, so I > would like to clarify that I am not being skeptic on "if we should support > tomcat" but on "how can we support tomcat + take full advantage of OSGi".
I'm not even sure that's possible :). Using ServiceMix in a Tomcat distro would be more about "reusing Tomcat" than "taking full advantage of OSGi". It will be interesting to see how OSGi-like we can make Tomcat, but I'd have thought the shared class loader stuff in Tomcat is always going to be fairly static though; not like OSGi where anything can be hot swapped at runtime and by using wacky class loaders you can hide packages or share different versions of the same package across deployment units. WARs can clearly be hot-swapped; am not sure if there'll be any hot swapping of the shared ServiceMix class loader stuff though. Though maybe its a bit like using statically typed languages like Scala in a REPL (which makes it seem like a totally dynamic scripting language when really its just compiling each line on the fly); we could maybe make the Tomcat version of ServiceMix look and feel like the dynamic OSGi world; its just when you upgrade/install/uninstall something shared, it just reboots Tomcat under the covers :). But then folks in production with Tomcat tend to do that anyway when undeploying WARs anyway :) Its worth remembering though that the aim isn't to turn Tomcat into OSGi (there's no point, there's already OSGi/Karaf if thats what you want :), its to bring the ServiceMix goodness to folks who prefer Tomcat as their general purpose application container. Tomcat and Karaf both rock and both have their pros and cons; though letting users choose is a good thing too IMHO. -- James ------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: jstrachan, fusenews Blog: http://macstrac.blogspot.com/ Open Source Integration and Messaging
