>>>>> "'Achim Nierbeck' via OPS4J" <[email protected]>:
> Hi Steinar, > yep, it's called the whiteboard pattern. > For that you just need to expose your servlets as services, the > whiteboard-extender of pax web will take care of the rest. Sounds exactly what I was looking for. :-) > For a full list of possibilities take a look at the following samples and > itests. > [1] lists the first whiteboard sample but I'm sure you're able to find the > other whtieboard-* samples as well ;) > [2], is just one of the possible tests, again there are a bunch of other > itests checking the various samples. > regards, Achim > [1] - > https://github.com/ops4j/org.ops4j.pax.web/tree/master/samples/whiteboard > [2] - > https://github.com/ops4j/org.ops4j.pax.web/blob/master/pax-web-itest/pax-web-itest-container/pax-web-itest-container-jetty/src/test/java/org/ops4j/pax/web/itest/jetty/WhiteboardServletAnnotatedIntegrationTest.java Thanks! I'm currently in the process of transforming my eaxample webapp from war to jar. https://github.com/steinarb/ukelonn/tree/using-vaadin/ukelonn.bundle Ie. making the webapp bundle a regular OSGi bundle with a regular internal layout, not a WAR-type layout. The regular bundle will register the servlet by having the activator listen for the WebContainer service and registering the servlet on that. Once I've got that approach up and working I will look into reversing the approach, ie. try to expose a service like in [2] above. -- -- ------------------ OPS4J - http://www.ops4j.org - [email protected] --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
