cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bin Zhu (JIRA)" <>
Subject [jira] [Commented] (CXF-4761) ensure CXF follow jaxws spec
Date Fri, 25 Jan 2013 10:09:13 GMT


Bin Zhu commented on CXF-4761:

Hi Freeman,
The Outbound SOAP message in current CXF is like below:
<soap:Envelope xmlns:soap="">
      <ns1:returnNullResponse xmlns:ns1="http://serverrpc.testdata.soapbinding.annotations/">
            <faultstring>Cannot write part return. RPC/Literal parts cannot be null.
(WS-I BP R2211)</faultstring>
We think that the reason we can't catch the WebServiceException in Client side is that CXF
wrapped the Fault in the common response element, which is not the correct behavior.
We also tested the SOAP message from AIX2 which our client can catch the WebServiceException
as expected and found that the Fault is not wrapped in the response element as CXF.
<soapenv:Envelope xmlns:soapenv="">
         <faultstring>Return argument(s) in operation method returnNull is null.  This
is not allowed for rpc/lit messages.</faultstring>

Based on the above analysis, we made a patch for it. can you help take a look at it? Thanks.
> ensure CXF follow jaxws spec
> ------------------------------------
>                 Key: CXF-4761
>                 URL:
>             Project: CXF
>          Issue Type: Test
>            Reporter: Freeman Fang
>            Assignee: Freeman Fang
>             Fix For: 2.5.9, 2.6.6, 2.7.3, 2.8.0
>         Attachments:, AnnotationsSoapBindingRpc2.ear, AnnotationsSoapBindingRpc.ear
> especially 
> Due to the limitations described in section 5.3.1 of the WS-I Basic Profile specification
(see [8]), null values cannot be used as method arguments or as the return value from a method
which uses the rpc/literal binding.
> ♦Conformance(NullValuesinrpc/literal): Ifanullvalueispassedasanargumenttoamethod,orreturned
from a method, that uses the rpc/literal style, then an implementation MUST throw a WebServiceException.

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:

View raw message