nillable="false" is the default. There's no need to include it in the
definition.
On 12/12/06, Jost Richstein <jrichstein_at_softdecc.com> wrote:
> Hi,
>
> I am using JWSDP 1.6 and run wscompile (and wsdeploy) with the
> -define option (reading my endpoint interface and define a service).
> wsdeploy generates a WSDL (rpc/enc). So far so good, everything works fine.
>
> What I am missing in the WSDL is the nillable attribute for elements.
> I have a complex type in the WSDL, lets say
>
> <complexType name="Date">
> <sequence>
> <element name="day" type="int"/>
> <element name="month" type="int"/>
> <element name="year" type="int"/>
> </sequence>
> </complexType
>
> What I would expect is a nillable="false", because that is way it is
> implemented in Datexxxx_doSerialize:
>
> ...((Integer)obj).intValue();
>
> and it is the way how my client proxies are generated (as int, not Integer).
> The same happens for type="boolean".
>
> Is there any way to get this nillable Attributes generated with wsdeploy
> (and have, at the same time, for other elements like string a
> nillable="true")?!
>
> Jost
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
> For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net
>
>