[
https://jira.jboss.org/jira/browse/JBMETA-39?page=com.atlassian.jira.plug...
]
Alexey Loubyansky commented on JBMETA-39:
-----------------------------------------
The XSD model group which does not enforce order restriction of its elements is xsd:all.
But elements in xsd:all must have maxOccurs='1' (or 0). In our case, only a few
types could switch from xsd:sequence to xsd:all, but most of the types can't. Also,
xsd:all cannot appear as a child in xsd:sequence, so grouping elements with
maxOccurs='1' under xsd:all in xsd:sequence will not work.
So, I think we should choose the order for the elements and stick to it.
jboss-client_5_0.xsd element order should not be required as its
inconsistent with previous dtds
------------------------------------------------------------------------------------------------
Key: JBMETA-39
URL:
https://jira.jboss.org/jira/browse/JBMETA-39
Project: JBoss Metadata
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.0.0.Beta15
Reporter: Scott M Stark
Assignee: Scott M Stark
Fix For: 1.0.0.CR1
The sequence declared by the xsd is inconsistent with the element ordering of previous
dtds. For all of these optional elements, the order should not matter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira