There has been some discussion about what maxOccurs="1" minOccurs="0"
means.
Currently the only way that axis can get this to flow over the wire
correctly is to map this as an array.
There needs to be a way to know if the value exists or not. Checking for
nill is not sufficient because there is no way
the current serializer can differentiate between ("nillable=true") and
(maxOccurs="1" minOccurs="0") cases.
So either meta data needs to be added to the class, or we continue to map
this as an array.
Rich Scheuerle
XML & Web Services Development
512-838-5115 (IBM TL 678-5115)
"St-Germain,
Sylvain" To: "Axis Dev (E-mail)"
<[EMAIL PROTECTED]>
<Sylvain.StGermain@ cc:
cognos.com> Subject: [wsdl2java] combining
maxOccurs="0" with maxOccurs="1" generates
data members as arrays, is this
normal?
02/27/2002 11:54 AM
Please respond to
axis-dev
Removing the minOccurs as below fixes it.
I get two strings instead of two arrays of strings, which is what I want.
<complexType name="cookie">
<sequence>
<element name="name" type="xsd:string" maxOccurs
="1"/>
<element name="value" type="xsd:string" maxOccurs
="1"/>
</sequence>
</complexType>
I think that maxOccurs="1" shouldn't generate an array.
--
Sylvain
This message may contain privileged and/or confidential information. If
you
have received this e-mail in error or are not the intended recipient, you
may not use, copy, disseminate or distribute it; do not open any
attachments, delete it immediately from your system and notify the sender
promptly by e-mail that you have done so. Thank you.
