wood burning stoves*
The moose likes Web Services and the fly likes xsd:choice AXIS and JAXWS Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCA/OCP Java SE 7 Programmer I & II Study Guide this week in the OCPJP forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "xsd:choice AXIS and JAXWS" Watch "xsd:choice AXIS and JAXWS" New topic
Author

xsd:choice AXIS and JAXWS

gauravzzz sharmazzz
Greenhorn

Joined: Aug 23, 2005
Posts: 1
Hi everyone,

I have a schema that needs to be sent across in SOAP message, please note that this schema is not controlled by us. I have attached an abridged version of this schema. The purpose for such a complicated schema is:
If A1 is present, it can also have A2
But if A1 is not present A2 has to be there

The schema for the same is attached at the end.

Problem is when I use AXIS, it creates a new var A22?? Cant seems to find the origin and the meaning of the schema is completely lost. On trying Jaxws, it just doesn�t create any arg structure code but creates a List. Can anyone help me with this problem?

The structure:
<xsd:complexType name="arg">
<xsd:sequence>
<xsd:choice>
<xsd:sequence>
<xsd:element name="A1" type="xsd:string"/>
<xsd:element minOccurs="0" name="A2" type="xsd:string"/>
</xsd:sequence>
<xsd:sequence>
<xsd:element name="A2" type="xsd:string"/>
</xsd:sequence>
</xsd:choice>
</xsd:sequence>
</xsd:complexType>

PS: The actual structure is much more complicated having many more condition, but this is the bare minimum I could reduce to.
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: xsd:choice AXIS and JAXWS