[
https://issues.apache.org/jira/browse/AMQ-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-2709.
-------------------------------
Resolution: Fixed
Fix Version/s: (was: 5.x)
5.6.0
The is fixed by the XBean 3.9 update in AMQ-3647 which now allows elements in
any order.
> Refactor core XML schema to use xs:all types in place of xs:sequence
> --------------------------------------------------------------------
>
> Key: AMQ-2709
> URL: https://issues.apache.org/jira/browse/AMQ-2709
> Project: ActiveMQ
> Issue Type: Improvement
> Affects Versions: 5.3.1
> Reporter: Fintan Bolton
> Fix For: 5.6.0
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
