On Aug 4, 2014, at 8:59 AM, neela <[email protected]> wrote:
> Hi,
> I am not a expert but by WSI-BP R2211 i think null is not allowed when its
> boolean.
>
> The WSI-BP R2211 is as below:
> R2211 An ENVELOPE described with an rpc-literal binding MUST NOT have the
> xsi:nil attribute with a value of "1" or "true" on the part accessors.
>
>
> So throwing a Fault when any input is null is not correct. (I think for
> string types we can have null)
Umm.. How? An empty part accessor (like <myValue />) is still not null.
That’s an empty string.
This looks correct to me. There isn’t a way to send a null as a parameter
with RPC/Lit according to the WSI-BP spec. The exception is correct.
Dan
>
> if (o == null) {
> //WSI-BP R2211 - RPC/Lit parts are not allowed to be
> xsi:nil
> throw new Fault(
> new
> org.apache.cxf.common.i18n.Message("BP_2211_RPCLIT_CANNOT_BE_NULL",
> LOG,
> part.getConcreteName()));
> }
>
>
> Please verify and if this qualifies for a JIRA.
>
> Thanks in advance.
>
> Regards,
> Neela
>
>
>
>
> --
> View this message in context:
> http://cxf.547215.n5.nabble.com/RPCOutInterceptor-java-WSI-BP-R2211-RPC-Lit-parts-are-not-allowed-to-be-xsi-nil-tp5747317.html
> Sent from the cxf-user mailing list archive at Nabble.com.
--
Daniel Kulp
[email protected] - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
