Thanks for the detailed reply.
Looking at HttpServiceServlet I can't help, but notice that the entire whiteboard seems to be anchored in a single ServletContext. Therefore it must multiplex access to this context to simulate multiple whiteboard web applications. This does not seem like a very easy/stable design to implement.
Would it be possible to introduce a service oriented solution along the lines of the Gemini Web web container adapter:
Implementations of this adapter have to be able to programatically talk to a concrete web container instance to make it create ServletContexts. From my experience with Tomcat it is not very hard to make a ServletContext (i.e. a web app internal structure) entirely programatically without any web.xml etc. metadata. It is also pretty easy to boot Tomcat from a bundle. I imagine it will be even easier on Jetty. Combine this with the programmatic servlet/filter/listener creation in Servlet 3.0 and it seems like a compelling design. Basically the whiteboard will only have to bridge Servlet 3.0 with the OSGi service registry.
Does such a (radical) redesign seem feasible?
Regards