mustafa created CXF-6319:
----------------------------
Summary: Regression: failing namespace resolution after CXF-5891
Key: CXF-6319
URL: https://issues.apache.org/jira/browse/CXF-6319
Project: CXF
Issue Type: Bug
Components: JAX-WS Runtime
Affects Versions: 2.7.15, 2.7.14
Reporter: mustafa
When using CXF 2.7.14 or later this request fails
{code:xml}
<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>
{code}
with the error
{code:xml}
<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>
{code}
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
