Bug 1207119

Description of problem:

When using CXF 2.7.14 (EAP 6.3.3+) or later this request fails

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <SOAP-ENV:Body xmlns:xs="http://www.w3.org/2001/XMLSchema">
      <ns0:echo xmlns:ns0="http://example.com">
         <ns0:s xsi:type="xs:string">hello</ns0:s>
      </ns0:echo>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

with the error

<Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP-ENV:Header xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"/>
   <soap:Body>
      <soap:Fault>
         <faultcode>soap:Server</faultcode>
         <faultstring>prefix xs is not bound to a namespace</faultstring>
      </soap:Fault>
   </soap:Body>
</soap:Envelope>

Prior to the changes for CXF-5891 this worked without any problems. Analysis from Red Hat engineering seems to say that it looks that all attributes and namespace settings in soap:envelop or soap:body elements are all ignored in ReadHeaderInterceptor and SAAJInInterceptor.

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


How reproducible:
Every time

Steps to Reproduce:
1. Send request using EAP 6.3.3/6.4.0
2. 
3.

Actual results:
Error is received saying prefix xs is not bound to a namespace

Expected results:
Sucessful response

Additional info: