Better check from time to time what Maven does in a complex project . We'll have to check how to get rid of all the jars needed for testing. In the meantime, I have removed at least the toxic items from the lib folder (osgi jars, javax.servlet, and, to be sure, also the jetty jars). Already after removal of the osgi jars, the deployment worked, and web:list and http:list look reasonable.
However, I still receive a 404 when calling the usual URL for the UI (myserver:8181/testwar). When checking the log, I found org.ops4j.pax.web.pax-web-extender-war throwing a warning that the class for which the WebServlet annotation was found could not be "created", and the class ....MyUI.Servlet wasn't loaded (the servlet class - extending VaadinServlet - is an inner class of the main UI class - extending the Vaadin framework class UI). The class exists in WEB-INF/classes as MyUI$Servlet.class. Should this combination still be supported by pax-web, or is this the point where my experiments to simply deploy the war in Karaf have to come to an end, and we have to go for a full OSGi integration of our Vaadin-based Web UI? Best Regards, Jochen -- View this message in context: http://karaf.922171.n3.nabble.com/pax-web-war-stays-in-deploying-state-tp4036280p4036363.html Sent from the Karaf - User mailing list archive at Nabble.com.
