Multiplicity Ordering in a Sequence or Choice

If you have multiplicity (such as maxOccurs) in a sequence or choice in a user-defined BOM, the XML generated may not be valid. (Multiplicity is supported in imported schemas or WSDLs.) This problem could occur if users write scripts to populate these sequences or choices, and add elements in an incorrect order. Note that elements will appear in the XML in the same order that they were added in the script.

For example, the following is an XSD fragment:

<xs:sequence maxOccurs="unbounded">
<xs:element name="fruit" type="xs:string" minOccurs="1" maxOccurs="1"/>
<xs:element name="cake" type="xs:int" minOccurs="1" maxOccurs="1"/>
</xs:sequence>