[CXF-4784] enhance CXF to follow jaxws spec 3.6.2.3 when using RI or Axis2 client

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.6.2, 2.6.5, 2.7.2
• Fix Version/s: 2.5.9, 2.6.6, 2.7.3, 3.0.0-milestone1
• Component/s: JAX-WS Runtime
• Estimated Complexity: Unknown
• Assignee: Freeman Yue Fang
• Reporter: Bin Zhu
• Created: 28/Jan/13 05:10
• Updated: 28/Feb/13 17:27
• Resolved: 28/Jan/13 06:30

Description

The content of the Outbound SOAP message in RPC/literal web service in current CXF is like below:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ns1:returnNullResponse xmlns:ns1="http://serverrpc.testdata.soapbinding.annotations/">
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>Cannot write part return. RPC/Literal parts cannot be null. (WS-I BP R2211)</faultstring>
</soap:Fault>
</ns1:returnNullResponse>
</soap:Body>
</soap:Envelope>
If we use RI/Axis2 client, then it will not catch the WebServiceException. The reason is that CXF wrapped the Fault in the common response element.
With this fix, the SOAP message in this scenario will be like below, which will catch the WebServiceException using RI/Axis2 client.
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>Cannot write part return. RPC/Literal parts cannot be null. (WS-I BP R2211)</faultstring>
</soap:Fault>
</soap:Body>
</soap:Envelope>