[CXF-6319] Regression: failing namespace resolution after CXF-5891

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.7.14, 2.7.15
• Fix Version/s: 3.1, 2.7.16, 3.0.5
• Component/s: JAX-WS Runtime
• Estimated Complexity: Unknown
• Assignee: Alessio Soldano
• Reporter: mustafa
• Created: 26/Mar/15 10:10
• Updated: 14/Oct/16 14:23
• Resolved: 30/Mar/15 08:31

Description

When using CXF 2.7.14 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.

Issue Links

• relates to: CXF-5891 ReadHeadersInterceptor performances improvement