Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@xml.apache.org
Date: 5 Nov 2002 19:15:28 -0000
Message-ID: <20021105191528.15156.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: axis-dev@xml.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 13439]  -
    Incorrect code generated from xsd:choice element in WSDL

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13439>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13439

Incorrect code generated from xsd:choice element in WSDL


------- Additional Comments From tomj@macromedia.com  2002-11-05 19:15 -------
Pretend for a minute that Axis doesn't fully support choice (which is easy).
If minOccurs=0, Axis is allowed to omit elements of a complex type.  If it is 
not, it must emit them with their value set to null.
On the other end, the value gets set to null either way.  Thus choice is 
simulated as only one property of the JavaBean is non-null.

What we really want here is a JavaBean that is recognized as a choice Object 
and handled in a slightly different way than a straight complexType JavaBean.

We should be able to set info in the meta-data to do this.