[
https://issues.jboss.org/browse/AS7-1923?page=com.atlassian.jira.plugin.s...
]
David Lloyd commented on AS7-1923:
----------------------------------
This is a bit more complicated than it seems. Some elements that are currently
<xs:sequence> may be able to be loosened to <xs:all>. However, XSD does not
support <xs:all> where some of the elements can appear more than one time. In this
case we should use <xs:sequence> in the XSD but parse it as though it were an
<xs:all>. This way if/when the new XML Schema standard comes out which supports
maxOccurrs > 1 in <xs:all>, we can change the element type without breaking
backwards compatibility.
Switch to version 1.1 of domain schema by default.
--------------------------------------------------
Key: AS7-1923
URL:
https://issues.jboss.org/browse/AS7-1923
Project: Application Server 7
Issue Type: Task
Components: Domain Management
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 7.1.0.Beta1
(At this stage 1.0 is only supported for parsing - discussion will continue re trying to
support minimum schema version or original schema version on marshalling)
- According to the schema the profile in server is mandatory but the parser does not
enforce this.
- The parser does not check that the extensions are defined in an extension element.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira