Jochen Wiedmann [mailto:[EMAIL PROTECTED] wrote:
> If you fix the order of the elements "Blah1", and so on by
> replacing the choice with
>
> <xs:element name="Blah1" minOccurs="0" maxOccurs="unbounded"/>
> <xs:element name="Blah2" minOccurs="0" maxOccurs="unbounded"/>
> <xs:element name="Blah3" minOccurs="0" maxOccurs="unbounded"/>
>
> then everything would be fine.
i had come to a similar conclusion.
however, (just so i understand the limitation) in that case i could have
an XML with...
<Foo>
<Bar>...</Bar>
<Blah1>...</Blah1>
<Blah1>...</Blah1>
<Blah3>...</Blah3>
<Blah3>...</Blah3>
<Blah3>...</Blah3>
</Foo>
but not...
<Foo>
<Bar>...</Bar>
<Blah1>...</Blah1>
<Blah3>...</Blah3>
<Blah1>...</Blah1>
<Blah3>...</Blah3>
<Blah2>...</Blah2>
<Blah3>...</Blah3>
</Foo>
(since they must occur in the order Blah1, then Blah2, then Blah3).
correct?
ps-any one have an estimate for when this will be fixed in jaxme?
thanks
bobD
--
Roberto Diaz
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
