[ARTEMIS-1720] Expose activemq.xsd to validate bootstrap.xml and management.xml

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.0
• Fix Version/s: 2.5.0
• Assignee: Justin Bertram
• Reporter: Lionel Cons
• Created: 02/Mar/18 08:56
• Updated: 02/Mar/18 21:03
• Resolved: 02/Mar/18 20:20

Description

As hinted in the documentation ("Configuration Reference" section), xmllint can be used to validate the Artemis configuration files.

This works fine with broker.xml:

$ xmllint --schema ${ARTEMIS_HOME}/schema/artemis-server.xsd broker.xml --noout
broker.xml validates

However, Artemis uses other XML configuration files like bootstrap.xml and management.xml and the same command fails to validate them:

$ xmllint --schema ${ARTEMIS_HOME}/schema/artemis-server.xsd bootstrap.xml --noout
bootstrap.xml:19: element broker: Schemas validity error : Element '{http://activemq.org/schema}broker': No matching global declaration available for the validation root.
bootstrap.xml fails to validate

$ xmllint --schema ${ARTEMIS_HOME}/schema/artemis-server.xsd management.xml --noout
management.xml:18: element management-context: Schemas validity error : Element '{http://activemq.org/schema}management-context': No matching global declaration available for the validation root.
management.xml fails to validate

xmllint is a very useful tool to catch configuration errors and all the XML configuration files used by Artemis should be validated this way.

Issue Links

• relates to: ARTEMIS-1605 RBAC back compatibility Issue in upgrading broker from 2.3
• links to: GitHub Pull Request #1927