Hi, I am looking for a solution for integrating a war based upon SpringMVC V4+ with Karaf/Jetty. Currently we have a working web app based upon SpringMVC/Security/Mobile V3 that uses SpringDM running on Karaf 2.3.2. We would like to continue with Spring but upgrade to version 4.
I was wondering if perhaps Achim with your pax-web experience or others had any thoughts on the following approach. By instructing the maven-bundle-plugin to use <Spring-Context> instead of <Bundle-Blueprint> then the blueprint-spring-extender (https://github.com/apache/aries/tree/trunk/blueprint/blueprint-spring-extender, thanks Guillaume) would be used to process the Spring namespaced config file e.g <plugin> <groupId>org.apache.felix</groupId> <artifactId>maven-bundle-plugin</artifactId> <configuration> <instructions> <Spring-Context>WEB-INF/track-trace-servlet.xml</Spring-Context> This much I have done and I can log the Spring beans in the application context and the osgi services to the Karaf console. However the Spring DispatcherServlet still needs to be registered and I thought that this could perhaps be achieved by programmatically implementing Springs WebApplicationInitializer (http://docs.spring.io/spring/docs/current/javadoc-api/org/springframework/web/WebApplicationInitializer.html). Assuming that the servlet container was able to find the class implementing the WebApplicationInitializer would this be sufficient? If so, any pointers on how to coax the servlet container to scan and find the customised WebApplicationInitializer? Thanks, Tim -- View this message in context: http://karaf.922171.n3.nabble.com/SpringMVC-V4-Karaf-tp4047917.html Sent from the Karaf - User mailing list archive at Nabble.com.
