[ https://issues.jboss.org/browse/JBWS-3888?page=com.atlassian.jira.plugin.... ] R Searls commented on JBWS-3888: -------------------------------- On evaluation I find this can not be an issue in JBossWS. For 3 reasons I recommend this be forwarded to the undertow team for evaluation. One, "metadata-complete" is an attribute of "web-app" in the web.xml file. Undertow handles the processing of that information. Two, annotations @WebServlet, @WebFilter, and @WebListener are to be ignored as well. I don't think JBossWS/CXF directly uses these or acts on them but web apps do. Three, the sample code provided by Amit was determine not to correctly show the issue. I would think there is a test in undertow to check this scenario. The Java Servlet 3.0 / 3.1 Specification states. "If metadata-complete is set to "true", the deployment tool only examines the web.xml file and must ignore annotations such as @WebServlet, @WebFilter, and @WebListener present in the class files of the application, and must also ignore any web-fragment.xml descriptor packaged in a jar file in WEB-INF/lib. If the metadata-complete attribute is not specified or is set to "false", the deployment tool must examine the class files and web-fragment.xml files for metadata,as previously specified." -- This message was sent by Atlassian JIRA (v6.3.11#6341)