Meaningless Drivel is fun!
The moose likes Web Services and the fly likes XSD generation Issue Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Web Services
Bookmark "XSD generation Issue" Watch "XSD generation Issue" New topic

XSD generation Issue

Andy Barky

Joined: Sep 17, 2005
Posts: 16
Hi ranchers,

I am developing the web service with bottom up approach.

Here is my main class method signature
public MPWResponse updateAccount(String userId, String buyer_Id, int prog_Id, String token, String fName, String lName, String zip, String email, String status, boolean registered)

and below is my WSDL entry
<xsd:import namespace="" schemaLocation="MainService_schema1.xsd"/>
<message name="updateAccount">
<part element="tns:updateAccount" name="parameters"/>
<message name="updateAccountResponse">
<part element="tns:updateAccountResponse" name="parameters"/>

and below is my XSD entry
<xs:element name="updateAccount" type="tns:updateAccount"/>

<xs:element name="updateAccountResponse" type="tns:updateAccountResponse"/>


<xs:complexType name="updateAccount">
<xs:element minOccurs="0" name="arg0" type="xs:string"/>
<xs:element minOccurs="0" name="arg1" type="xs:string"/>
<xs:element name="arg2" type="xs:int"/>
<xs:element minOccurs="0" name="arg3" type="xs:string"/>
<xs:element minOccurs="0" name="arg4" type="xs:string"/>
<xs:element minOccurs="0" name="arg5" type="xs:string"/>
<xs:element minOccurs="0" name="arg6" type="xs:string"/>
<xs:element minOccurs="0" name="arg7" type="xs:string"/>
<xs:element minOccurs="0" name="arg8" type="xs:string"/>
<xs:element name="arg9" type="xs:boolean"/>

I am trying to print userId instead of arg0 in XSD. This name parameter has only "arg0" and so on in XSD. Everytime, I generate the WSDL and XSD automatically, It overwrites. I am using the eclipse and windows. Does anybody have any idea how this can be achieved?

Thanks for help in advance,


- WS rookie

I agree. Here's the link:
subject: XSD generation Issue
It's not a secret anymore!