[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Problem using <xsd:all>

• From: Paul Stepowski <paul.stepowski@i...>
• To: Dennis Sterzenbach <lists@r...>, xml-dev@l...
• Date: Tue, 02 Oct 2007 17:51:12 +1000

Dennis Sterzenbach wrote:
> Hi Paul!
> 
> Paul Stepowski wrote:
> <snip />
>>   <xsd:element name="task">
>>     <xsd:complexType>
>>       <xsd:sequence>
>>         <xsd:element ref="tasklist:prerequisites" minOccurs="0"
>>           maxOccurs="1" />
>>         <xsd:all>
>>           <xsd:element ref="tasklist:success" minOccurs="1"
>>             maxOccurs="1" />
>>           <xsd:element ref="tasklist:failure" minOccurs="1"
>>             maxOccurs="1" />
>>         </xsd:all>
>>       </xsd:sequence>
>>       <xsd:attribute name="id" type="xsd:string" use="required" />
>>     </xsd:complexType>
>>   </xsd:element>
> <snip />
>> "The content of 'sequence' must match (annotation?, (element | group | choice |
>> sequence | any)*). A problem was found starting at: all."
>>
>> According to the w3c, all is a valid tag.  Can anyone shed some light on this error?
> 
> These are valid tags, but unfortunately not in that order.
> As far as I know you can't use <xsd:all> inside a sequence:
> 
> "Parent elements: group, complexType, restriction (both simpleContent
> and complexContent), extension (both simpleContent and complexContent)"
> 
> Best regards
> -- Dennis Sterzenbach

Thanks Dennis,

My next question is then, can I achieve the same effect with a different syntax?
 I need to specify <success> AND <failure> both occuring once each (in any
order).

Thanks,

Paul

• Follow-Ups:
  • Re: Problem using <xsd:all>
    • From: George Cristian Bina <george@o...>

• References:
  • Problem using <xsd:all>
    • From: Paul Stepowski <paul.stepowski@i...>