[
https://issues.apache.org/jira/browse/CXF-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13564047#comment-13564047
]
Bin Zhu commented on CXF-4784:
------------------------------
Uploaded the patches for this issue, can you help review it? Thanks.
> 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.6.2, 2.6.5, 2.7.2
> Reporter: Bin Zhu
> Attachments: CXF-4784.patch
>
>
> 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
