Jetty has a long history of being lightweight and easily embeddable, with a good and responsive community, that's why it was chosen to be used in pax-web, and pax-web was really the only available solution at some point hence we have chosen it for Karaf. I don't really see any major problems deploying gemini web in Karaf though I haven't actually tested it. The question is why do you want to use Tomcat instead of Jetty ? Jetty is very mature too, though a bit less known.
Doing the WAB support in OSGi is quite a lot of work and we have people here maintaining pax-web, so I don't really see the point in recreating a new container on top of Tomcat. The most important thing about Tomcat imho is that the container and management is well known, but if we'd start embedding it, you'd loose all of that anyway. On Tue, May 22, 2012 at 10:11 PM, Romain Gilles <romain.gil...@gmail.com> wrote: > Hi all, > I would like to know if any of you have run or run a tomcat web container as > a Http Service and Web Application Service... > Do I have to install eclipse gemini web on karaf to test it? I have had a > look to pax web and the only spi provider is Jetty. Is there a reason that? > Tomcat is an Apache project and the current osgi integration is done by the > eclipse community and Jetty is now a eclipse project and is currently the > default web container of karaf (an apache project ...)? > > Romain. -- ------------------------ Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ FuseSource, Integration everywhere http://fusesource.com
