Or in other words, I found that the terms enwrapped with the
<Xs:choice> </xs:choice> and <xs:all> </xs:all> or just use the
<xs:sequence> </xs:sequence>
These complexTypes are serialized into the javatypes,
They are basically the same. I can not see any logic in the
created javacode. I am not sure whether I am wrong?
<xs:complexType name="example">
<xs:sequence>
<xs:choice maxOccurs="unbounded">
<xs:element name="a" type="x:aa" />
<xs:element name="b" type="x:bb" />
</xs:choice>
</xs:sequence>
</xs:complexType>
the above the maxOccurs seems have no effect at all.
<xs:complexType name="example">
<xs:sequence>
<xs:all maxOccurs="unbounded">
<xs:element name="a" type="x:aa" />
<xs:element name="b" type="x:bb" />
</xs:all>
</xs:sequence>
</xs:complexType>
any Sugestions? I am wondering whether I have to implement the "choice",
"all" myself? Can the Axis WSDL2Java can do it for me ?
thank u very much
jiadao
-----Original Message-----
From: jiadao [mailto:[EMAIL PROTECTED]
Sent: Montag, 24. Mai 2004 17:50
To: [EMAIL PROTECTED]
Subject: RE: AXIS - jms transaction
Hi,
I am wondering that whether the AXIS has implemented all the XML
schema ,the JAX-RPC specification 1.1, for example the <xs:choice>,
<xs:all> and so on. Can the WSDL2Java do all the serialization and
deserialization of the java types between the xml types which conforms
to the xml schema.
thank very much!
jiadao
.
