The order of the child elements that appear inside the broker element
must now appear in the order defined by the XML schema. In versions
prior to 5.4.0, the element order was unimportant, because the XML configuration file was
not validated. In version 5.4.0, however, the configuration file is validated against the
ActiveMQ XML schema as it is loaded.
Fortunately, the element order is easy to remember, because it is always alphabetical (the XML schema is automatically generated by the XBeans utility, so alphabetical ordering is guaranteed).
In ActiveMQ 5.4.0, when deploying into the OSGi container, you have the option of embedding the broker XML inside a Blueprint configuration file, instead of using a Spring configuration file. The ActiveMQ Blueprint schema belongs to the following namespace:
http://activemq.apache.org/schema/blueprint