geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rakesh Midha" <>
Subject Re: Reason for sequence in XSD's
Date Mon, 15 Jan 2007 06:14:23 GMT
David, you are right about only web app j2ee xsd using choice, and some
parts of j2ee application xsd.

As Aaron, said there are number of users reporting error which turned out to
be sequence error. Infact I myself have struggled some time because I tend
to forgot that order has to be maintained. Using choice in place of sequence
help you specially when you copy paste some elements.

Jason, about "a case where it would be necessary to change the order of the
elements", there is no such requirement or case where it is necessary but I
consider sequence as an extra unrequired restrictions and people definatly
don't like redundent thinks and specially "redundent restrictions"


On 1/15/07, Aaron Mulder <> wrote:
> We have seen a number of errors on the user list that turned out to be
> plans with elements in the wrong order.  I'd have preferred if there
> wasn't a specific order I think, but I don't feel strongly enough to
> want to change all the schemas.
> Thanks,
>       Aaron
> On 1/14/07, Jason Warner <> wrote:
> >
> >
> > >
> > > >>
> > > >> Anyone got an idea, why it is so? I hope I am not missing something
> > > >> important here.
> > >
> > > >I think it was mostly my preference plus a vague attempt to imitate
> > > >the spec schemas.  It's definitely not written in stone :-)  Maybe we
> > > >should see what other people like.
> >
> >  I think it is generally easier to pick up and learn and if there is a
> set
> > order to the elements.  Also, I think it makes it easier to go from one
> > document to another if you know where to look in the document for the
> > specific element you might be looking for.  Is there a specific reason
> to
> > not have a set order?  I'm having trouble imagining a case where it
> would be
> > necessary to change the order of the elements.
> >
> >

View raw message