Thanks for the hints, Achim! Now it works - basically. The trick was to move out the servlet class from the Vaadin main UI class. It looks like pax-web cannot deal with the servlet defined as inner class (TestwarUI$Servlet.class).
I still have some problems: when installing the bundle as a wab (just with install file:..., manifest of course filled accordingly), the WebAppParser in org.ops4j.pax.web.pax-web-extender-war does not scan for annotated classes. So this deployment does not work if I use the @WebServlet annotation, but I have to include the respective definitions in the web.xml. When I install the bundle as plain war (install webbundle:file:...), it scans for annotated classes and uses the @WebServlet annotation correctly. Any idea what I have to do to trigger the scanning also for wab deployment? I also receive a "java.lang.AssertionError: Not a File: /org/atmosphere/annotation" and it is not possible to access some resources since the war is not extracted. Maybe I just have to find where to set extractWars to true for jetty running in Karaf. Regards, Jochen -- View this message in context: http://karaf.922171.n3.nabble.com/pax-web-war-stays-in-deploying-state-tp4036280p4036414.html Sent from the Karaf - User mailing list archive at Nabble.com.
