You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@cxf.apache.org by Benson Margulies <bi...@gmail.com> on 2008/01/24 03:41:28 UTC

WebParam vs. nillable

While exercising the JavaScript code, I coded a doc/lit/bare service
with a parameter of type SomeClass[].

The WSDL says that the resulting item is nillable.

However, at runtime, JAXB doesn't act as if it is nillable.

How do we communicate the type information for JAX-WS parameter items
into JAXB in the first place?

Re: WebParam vs. nillable

Posted by Daniel Kulp <dk...@apache.org>.

Isn't this the same bug as what you logged?
https://issues.apache.org/jira/browse/CXF-1266

Dan



On Wednesday 23 January 2008, Benson Margulies wrote:
> While exercising the JavaScript code, I coded a doc/lit/bare service
> with a parameter of type SomeClass[].
>
> The WSDL says that the resulting item is nillable.
>
> However, at runtime, JAXB doesn't act as if it is nillable.
>
> How do we communicate the type information for JAX-WS parameter items
> into JAXB in the first place?



-- 
J. Daniel Kulp
Principal Engineer, IONA
dkulp@apache.org
http://www.dankulp.com/blog