Thanks for the quick reply Michael. I made that change but there is no improvement. Here are the relevant parts of my server-side class:

public class MyMessage implements java.io.Serializable
{
 private String uid;
 private String content;

 public MyMessage() {}

 public String getUid() { return uid; }
 public void setUid(String uid) { this.uid = uid; }

 public String getContent() { return content; }
 public void setContent(String content) { this.content = content; }
};

I updated my JWS source file (and deleted the corresponding class file, just to be safe), restarted Tomcat, and requested the WSDL by invoking http://localhost:8080/axis/MyWebService.jws?wsdl and here are the (unexpected) results:

<complexType name="MyMessage">
 <sequence>
 <element name="content" nillable="true" type="xsd:anyType" />
 <element name="uid" nillable="true" type="tns2:String" />
 </sequence>
</complexType>

Am I still writing my Java class incorrectly?


From: "Michael Oliver" <[EMAIL PROTECTED]>
Reply-To: <[EMAIL PROTECTED]>
To: <axis-user@ws.apache.org>
Subject: RE: 1.2.1 autogen WSDL seems to be wrong
Date: Wed, 24 Aug 2005 07:34:23 -0700

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 [EMAIL PROTECTED]

-----Original Message-----
From: Jarmo Doc [mailto:[EMAIL PROTECTED]
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/



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

Reply via email to