The current drawback of this solution is that the standard OSGi http service does not support adding filters or servlet listeners. So as soon as you're having these things in your webapp it's not working out of the box with a standard http service. There is an upcomming spec for this for the R4.2 (a draft can be downloaded from the OSGi website); so as soon as implementations for this new spec are available you might be able to run any webapp in every OSGi container.
Carsten Bertrand Delacretaz wrote: > Hi, > > A while ago, Carsten pointed me to the Pax Web Extender - War [2] > service, an extender bundle that makes possible to deploy WAR files > into OSGi. > > As this might be interesting in some integration scenarios, or to keep > JEE developers happy, I have created a prototype webapp that can be > loaded in Sling as an OSGi bundle. > > See the README file at [1] for details - feedback is welcome. > > -Bertrand > > [1] > http://svn.apache.org/repos/asf/incubator/sling/whiteboard/bdelacretaz/pax-webapp/ > [2] http://wiki.ops4j.org/display/ops4j/Pax+Web+Extender+-+War > -- Carsten Ziegeler [email protected]
