Altova Mailing List Archives>Archive Index >xmlschema-dev Archive Home >Recent entries [Thread Prev] >Thread Next - Re: Ignore Order while validating XSD Re: Ignore Order while validating XSDTo: xmlschema-dev@--.--- Date: 1/24/2009 3:52:00 PM There=B4s much time since the last message, but I have a problem with the
given solution.
Since I use the model below, I can=B4t force the element to be declared, or=
in
other words, the minOccurs does not run.
The piece of code given from "George Cristian Bina":
<xs:complexType>
<xs:choice maxOccurs="unbounded">
<xs:element name="a"/>
<xs:element name="b"/>
<xs:element name="c"/>
<xs:element name="x"/>
</xs:choice>
</xs:complexType>
Suppose I wish the <xs:element name="a"/> to always be received, so I
change the code to the code below, but the minOccurs does not run.
<xs:complexType>
<xs:choice maxOccurs="unbounded">
* <xs:element name="a" minOccurs="1"/>*
<xs:element name="b"/>
<xs:element name="c"/>
<xs:element name="x"/>
</xs:choice>
</xs:complexType>
Does anyone has an idea how can I solve this?
Thanks a lot!
Dervillo
| ||||||
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site | |||
|
