Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
5.3.1
-
None
-
None
Description
It is much more convenient to use xs:all instead of xs:sequence in a schema that describes a configuration file. In a configuration file, it normally does not matter what order you insert child elements inside a parent element. Having to remember the arbitrary sequence in which the elements appear in the schema is a pain!
For example, when I went to insert a <networkConnectors> element inside a <broker> element, I was surprised to find that my XML editor complaining that this was not schema compliant. It turns out that I have to insert the <networkConnectors> element in exactly the right spot in order to comply with the schema.
This change would also be backward compatible with existing XML files.
Attachments
Issue Links
- is duplicated by
-
AMQ-2939 Disable Spring 3 schema validation
- Resolved