axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Oliver" <ol...@alariussystems.com>
Subject RE: 1.2.1 autogen WSDL seems to be wrong
Date Wed, 24 Aug 2005 14:34:23 GMT
Your class should be more consistent with the JavaBeans standard with
private members that are 'tall' and 'rich' with getters 'isTall' and
'isRich' and setters 'setTall' and 'setRich' and I wager the Java2WSDL will
be more consistent as well.

Michael Oliver
CTO
Alarius Systems LLC
6800 E. Lake Mead Blvd, #1096
Las Vegas, NV 89156
Phone:(702)643-7425
Fax:(702)974-0341
*Note new email changed from oliverm@matrix-media.com

-----Original Message-----
From: Jarmo Doc [mailto:jarmod@hotmail.com] 
Sent: Wednesday, August 24, 2005 7:29 AM
To: axis-user@ws.apache.org
Subject: 1.2.1 autogen WSDL seems to be wrong

I've written a simple web service (JWS) that includes a method that returns 
a complex type (well hardly "complex", just a couple of strings and 
booleans). The auto-generated WSDL (using Axis 1_2_1 final) for this web 
service makes no sense to me. For example, I have two booleans in my complex

type, something like this:

class Person
{
public boolean istall;
public boolean isrich;
};

Yet the WSDL indicates:

<element name="istall" type="xsd:anyType" />
<element name="isrich" type="tns3:boolean" />

Note the two different WSDL types for identical (boolean) Java types. Is 
this likely to be a bug in Axis 1_2_1 final?  Should I be using a different 
version (which?)

Thanks.

_________________________________________________________________
Don't just search. Find. Check out the new MSN Search! 
http://search.msn.click-url.com/go/onm00200636ave/direct/01/



Mime
View raw message