It was discovered that the Webservices DUP in previous versions of JBoss EAP 6 carried a bug that prevented it from scanning all visible classes with the @WebService annotation. An error presented when a `war` archive that contained a `web.xml` with a <servlet-class> that refers to a JAX-WS endpoint (so the class is annotated with @WebService) was located within an `ear` archive and the `jar` containing the class was located in the `ear` archive's `lib/` directory. The relevant code has been amended in this release to scan more thoroughly for @WebService classes and the error no longer presents.
Sample use case: You have a .war in an .ear, and the .war has a web.xml with a <servlet-class> that refers to a JAX-WS endpoint, so the class is annotated with @WebService. If that class is packaged in a jar found in the ear's lib directory, the JBossWS DUP won't pick it up, and then Undertow will throw an error like this (except of course the JBossWeb equivalent):
UT010009: Servlet ClientEndpoint of type class com.redhat.gss.jaxws.ClientEndpoint does not implement javax.servlet.Servlet
Alessio Soldano <email@example.com> updated the status of jira WFLY-3067 to Resolved
Verified on EAP 6.3.0 ER2
Changed <filename></filename> tags in Doc Text to ticks (`) to fix Bug 1096865