You need to define a 'choice' element between your two types. Then you can define multiplicity on this choice element e.g. by using a sequence.
-----Original Message----- From: Asaf Lahav [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 18, 2006 7:09 PM To: user@xmlbeans.apache.org Subject: RE: a simple xsd question What would be the best way to define a complex type without forcing a specific order of elements? -----Original Message----- From: cbryant [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 18, 2006 5:50 PM To: user@xmlbeans.apache.org Subject: Re: a simple xsd question xs:sequence tags define an ordered sequence of elements. Therefore, the provided XML is invalid because the sequence of SubmitPurchaseOrder child elements does not match the sequence in the XSD. Switching the argx and argy tags (in the XML or the XSD) will result in a valid document. Regards, Coram -- View this message in context: http://www.nabble.com/a-simple-xsd-question-tf2467386.html#a6879329 Sent from the Xml Beans - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
