Ah, sorry. Had some spelling errors here. It's actually the WebApplication that is a servlet registered inside HttpService. WebContainer is just managing the varous contexts.
On Sun, Aug 16, 2009 at 11:00 PM, Sten Roger Sandvik <[email protected]> wrote: > Hi all. > > I have slowly began to create an implementation of WebContainer (RFC66). > This allows us to deploy unmodified WAR files inside a OSGi engine. I have > added a contribution (but not yet approved) for a more extenisble > HttpService implementation and is trying to build the RFC66 using the same > principle. Some toughts: > > * Build a WebContainer implementation using any HttpService > implementation. > * A WebContainer is actually a Servlet registered inside the HttpService. > * Routes servlet calls to a servlet, filter or static resource inside the > WebContainer. > * All requests will be wrapped so that it behaves as it is in it's own > context. > * Sessions will be backed up by the "real" container, but scoped with > WebContainer id (or context). > > The general idea is to create the WebContainer so that it will run on any > HttpService. This means that we can have full RFC66 functionality even > inside your favorite web container. What do you guys think? > > // srs > >
