You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Bin Zhu (JIRA)" <ji...@apache.org> on 2013/01/28 06:11:12 UTC
[jira] [Created] (CXF-4784) enhance CXF to follow jaxws spec
3.6.2.3 when using RI or Axis2 client
Bin Zhu created CXF-4784:
----------------------------
Summary: enhance CXF to follow jaxws spec 3.6.2.3 when using RI or Axis2 client
Key: CXF-4784
URL: https://issues.apache.org/jira/browse/CXF-4784
Project: CXF
Issue Type: Bug
Components: JAX-WS Runtime
Affects Versions: 2.7.2, 2.6.5, 2.6.2
Reporter: Bin Zhu
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira