[#MB-984] Improve ActiveMQ's XSD to allow elements to appear in any order

FUSE Message Broker

Improve ActiveMQ's XSD to allow elements to appear in any order

Created: 13/Oct/11 03:25 PM Updated: 19/Jan/12 11:13 AM

Component/s:

broker

Affects Version/s:

5.5.1-fuse-00-06

Fix Version/s:

5.5.0-fuse-00-xx, 5.6.0-fuse-00-00, 5.5.1-fuse-02-02

Environment:

applicable to all envs

External Issue URL:

https://issues.apache.org/jira/browse/AMQ-3570

Description

« Hide

By default, ActiveMQ requires its XML config file to be validated, this is good to catch typos.

However, the XSD file being used forces us to have elements in a given order (currently alphabetical see http://activemq.apache.org/xml-reference.html - Schema Validation - Alphabetically Ordered XML Elements (New in 5.4))
Customer believes this leads to 'config files where related elements are not always in "logical" order.' AFAIK, this restriction is not in Apollo

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

Hiram Chirino added a comment - 27/Oct/11 01:18 PM

Opened https://issues.apache.org/jira/browse/AMQ-3570 to track change at apache.

[ Permlink | « Hide ]

Hiram Chirino added a comment - 27/Oct/11 01:21 PM

Fixed in apache trunk rev 1189740
This will eventually make it into the next major FUSE release.

[ Permlink | « Hide ]

Gary Tully added a comment - 16/Dec/11 11:35 AM

This needs a release of apache xbean 3.9, the new dependent feature is currently only available in a 3.9-SNAPSHOT but we can't release with a snapshot dependency.

[ Permlink | « Hide ]

Gary Tully added a comment - 19/Jan/12 11:13 AM

5.5.x and 5.5.1 branches now have xbean 3.9 dependency and support unordered elements.