Hello.
I'm tracing this through to try and understand why Jersey Servlet Initializer is not invoked for a pure Jaxrs applications running in Karaf 4.3.0. It appears the way that the ServletContainerInitializerScanner in the pax-web-api has a fundamental design flaw when it searches bundles for instances of the /META-INF/services/ ServletContainerInitializerScanner file. Namely that it only searches dependent bundles of the one that is being initialised. As the implementation of any service is meant to be hidden by the API, it means that you will never be able to initialise any web servlet. As such the pax-jetty-web adds the bodge of wiring-in itself to all web-context so its contextInitializer code can be discovered, but no other implementations. Rather than performing a bundle scan each time, surely jetty should be implementing the bundle listener pattern and have the set of servlet initializers that are available in the platform? Or am I missing something? Cheers, Paul -- -- ------------------ 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/ops4j/e9d0b4ab-33d7-4895-8a0f-e6d55e3e3b43n%40googlegroups.com.
