Hi, sorry for the missing links :-) [1] - https://github.com/ops4j/org.ops4j.pax.web/blob/master/samples/war-spring-osgi/src/main/webapp/WEB-INF/web.xml#L12-L15 [2] - https://github.com/ops4j/org.ops4j.pax.web/tree/master/samples/war-spring
regarding the scenario, could you provide a stripped down sample for me to use as integration test for verification? regards, Achim 2015-08-28 8:23 GMT+02:00 rsteppac <[email protected]>: > Achim, I think you forgot to provide the links to the examples you are > describing. > > Spring WS indeed requires a Spring context for its configuration. You can > instantiate the MessageDispatcherServlet in the blueprint context, but you > have to pass it the location of a Spring context file so it can initialize > properly. I use the ApplicationContextInitializer (bean id > "springWsContextInitializer") to transfer the camel endpoint mapping bean > that was instantiated in the blueprint context over to the spring context. > This works nice and dandy in Karaf 3. I have the feeling that the setup as > such works with Karaf 4 as well. The Camel context successfully starts. The > failure is only after when the whiteboard service picks up the spring WS > servlet that was published in the blueprint context. > > Ralf > > > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Nullpointer-Exception-in-jetty-ContextHandler-on-4-0-0-M2-and-M3-tp4041050p4042108.html > Sent from the Karaf - User mailing list archive at Nabble.com. > -- Apache Member Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS> Software Architect / Project Manager / Scrum Master
