[
https://issues.apache.org/jira/browse/ARTEMIS-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16376589#comment-16376589
]
ASF GitHub Bot commented on ARTEMIS-1661:
-----------------------------------------
GitHub user michaelandrepearce opened a pull request:
https://github.com/apache/activemq-artemis/pull/1896
ARTEMIS-1661 Support splitting of broker.xml
Support XML standard XInclude thus allowing splitting of the broker.xml
Added test cases with split out config using import.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/michaelandrepearce/activemq-artemis XInclude
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/1896.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1896
----
commit 7cc3de427af824367276ec1232e6874e4bf0705b
Author: Michael André Pearce <michael.andre.pearce@...>
Date: 2018-02-26T09:31:21Z
ARTEMIS-1661 Support splitting of broker.xml
Support XML standard XInclude thus allowing splitting of the broker.xml
Added test cases with split out config using import.
----
> Enable splitting of broker.xml into multiple files
> --------------------------------------------------
>
> Key: ARTEMIS-1661
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1661
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Reporter: Adi Rubin
> Priority: Minor
>
> Hi,
> Broker.xml contains both server configuration (connectors, cluster config
> etc) and addresses/queues. It would be useful to be able to move the
> <addresses> element to a separate file(s). An example use case would be
> generation of addresses using a script.
> Ideally, this should apply to all configuration elements in broker.xml.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
