AW: XSD to WSDL Translation

[Zedler, Michel]

Because Axis does only understand very basic XML Schema concepts.

If you are not happy with the generated WSDL

you can provide your own WSDL by adding a <wsdlFile> tag to you deployment descriptor ("deploy.wsdd").

See http://www.osmoticweb.com/axis-wsdd/

If you also want you schema to be reflected in your generated binding classes

you might be interested in the castor project.

See http://www-106.ibm.com/developerworks/webservices/library/ws-castor/

and http://www.castor.org/

 

Hope this helps,

Michel Zedler

-----Urspr�ngliche Nachricht-----
Von: venkatesh chandrasekaran [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 3. August 2004 03:33
An: [EMAIL PROTECTED]
Betreff: XSD to WSDL Translation

Hi,
In our xsd, we've an XOR choice.

Following is the snippet of xsd...
-------------------------------------------------------
<xs:choice>
  <xs:element ref="profile:Male"/>
  <xs:element ref="profile:Female"/>
</xs:choice>
<xs:element ref="profile:Location" minOccurs="0"/>
-------------------------------------------------------

When this gets converted into wsdl we can see the following snippet in wsdl...

wsdl is viewed like below in a browser
Go to browser
1) http://localhost:8080/axis(this is where our service is deployed)
2) Click the view link in the sentence "View the list of deployed Web services "
3) Click the wsdl link against your service.

WSDL Snippet
-------------------------------------------------------
<element name="Male" nillable="true" type="tns3:Sex_Type" />
<element name="Female" nillable="true" type="tns3:Sex_Type" />
<element maxOccurs="1" minOccurs="0" name="Location" nillable="true"    type="tns4:Location_Type" />
-------------------------------------------------------

QUESTION IS :
Why the choice tag(XOR option) in xsd is not reflected in wsdl?
Location tag with minouccurs=0 is translated from xsd to wsdl.(Please refer the above xsd and wsdl snippets)

Expecting your reply

Thanks
Venkatesh C