«

In my schema file, I have defined a choice as follows:

<xs:complexType name="myChoicesType">
<xs:choice>
<xs:element name="choice1" type="xs:string/>
<xs:element name="choice2" type="xs:string"/>
<xs:element name="choice3" type="xs:string"/>
</xs:choice>
</xs:complexType>

When a client using axis creates an instance document and chooses
choice1, axis is doing the following:

<choice1>blah...blah..blah></choice1>
<choice2 nil="true"/>
<choice3 nil="true"/>

Why is axis including choice2 and choice3 in the instance document
with the nillable attribute set? Is it possible to not have it
include choices that are left out.

Hi,

DayCoder <> writes:

> In my schema file, I have defined a choice as follows:
>
> <xs:complexType name="myChoicesType">
> <xs:choice>
> <xs:element name="choice1" type="xs:string/>
> <xs:element name="choice2" type="xs:string"/>
> <xs:element name="choice3" type="xs:string"/>
> </xs:choice>
> </xs:complexType>
>
> When a client using axis creates an instance document and chooses
> choice1, axis is doing the following:
>
> <choice1>blah...blah..blah></choice1>
> <choice2 nil="true"/>
> <choice3 nil="true"/>

Seems like a bug in Axis. This XML is not even valid per your
schema. I suggest that you report this to the Axis developers.


-boris

--
Boris Kolpackov
Code Synthesis Tools CC
http://www.codesynthesis.com
Open-Source, Cross-Platform C++ XML Data Binding