It's interesting that #3 works for you. I have an operation such as (and
note that it's java.lang.Boolean, not boolean):
public void update(Employee [] employees, Boolean sacked)
java2wsdl generates the following:
<element name="update">
<complexType>
<sequence>
<element maxOccurs="unbounded" name="employees" type="impl:Employee"/>
<element name="sacked" type="xsd:boolean"/>
</sequence>
</complexType>
</element>
When I create an Axis 1.3 client stub from this WSDL, I get the signature:
public void update(Employee [] employees, boolean sacked)
Hence I cannot supply null, I can only supply true/false. Adding
nillable="true" to the 'sacked' element in the WSDL and re-generating the
client stub does *not* correct this behavior.
Any idea what could be different about your situation that makes it work for
you?
From: Todd Orr <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
Subject: Re: Axis 1.3 suitable for production env?
Date: Tue, 10 Jan 2006 10:25:43 -0800
#3 - This just isn't true. I have many Boolean fields defined. Watching the
debugger I can plainly see that they come in as null if not provided.
On 1/10/06, Jarmo Doc <[EMAIL PROTECTED]> wrote:
>
> I do use document/literal.
>
>
> On #3, I don't have a solution yet so may have to create an intermediate
> class that contains the Booleans and then pass that class to the
operation
> rather than passing the contained Booleans.
>
> > > 3. Boolean parameters to operations appear to be converted to
> intrinsic
> > > booleans (note lowercase) in an Axis client so you can only pass
> >true/false
> > > when you need to be able to pass true/false/null.
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
