When a contract-first endpoint references a wsdl file which is not in the expected location (for instance under META-INF instead of WEB-INF/classes/META-INF for an EJB3 WS endpoint packaged in a war deployment), the JBossWS stack might fail in resolving the wsdl, while cxf properly uses it.
The stack needs to be able to resolve the wsdl the same as cxf and eventually early abort the deployment processing if the wsdl still can't be found.