+++ This bug was initially created as a clone of Bug #1150931 +++

Description of problem:
Platform BZ for https://issues.apache.org/jira/browse/CXF-5753

Since EAP 6.2.2, when a JAX-WS handler is configured on a WS endpoint even though it's an empty handler, SOAP requests like the following one start to face "Unmarshalling Error".

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Header/>
   <soapenv:Body>
      <hello xmlns="http://ws.samples.redhat.com/">
         <name xmlns="">SoapUI</name>
      </hello>
   </soapenv:Body>
</soapenv:Envelope>

Note how the default xml namespace is declared for both <hello> and <name>. However the soap request above might be invalid with regard to SOAP spec, until EAP 6.2.1 the same SOAP request worked so it should be a regression bug.

The same issue was reported and already fixed at https://issues.apache.org/jira/browse/CXF-5753. I confirmed that in fact the issue is resolved since CXF 2.7.12, so simply upgrading CXF to latest 2.7.x would fix the issue as well on EAP.


Version-Release number of selected component (if applicable):
Apache CXF 2.7.10


How reproducible:
100%


Steps to Reproduce:
1. Deploy the attached reproducer to EAP.
2. Send the above SOAP message to the endpoint using SoapUI.

Actual results:
Got the following error.

WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (http-/127.0.0.1:8080-1) Interceptor for {http://ws.samples.redhat.com/}GreetingServiceService#{http://ws.samples.redhat.com/}hello has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Unmarshalling Error: unexpected element (uri:"http://ws.samples.redhat.com/", local:"name"). Expected elements are <{}name> 
...
Caused by: javax.xml.bind.UnmarshalException: unexpected element (uri:"http://ws.samples.redhat.com/", local:"name"). Expected elements are <{}name>


Expected results:
Response should be returned successfully.