Re: Nillable and -define

From: Jost Richstein <>
Date: Wed, 7 Mar 2007 09:17:30 -0800 (PST)

My problem with this one was:

If I try to generate proxies from Axis 1.4 for a WSDL with that structure it
handle it like nillable=true. In other words it will use the wrapper

That makes a difference in the handling of that classes: I have to
explicitly set every
attribute in order to avoid a 'null'. That would not be nessesary using the

Anne Thomas Manes wrote:
> nillable="false" is the default. There's no need to include it in the
> definition.
> On 12/12/06, Jost Richstein <> 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:
>> For additional commands, e-mail:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

View this message in context:
Sent from the JAX-RPC - User mailing list archive at