Justin Bertram commented on ARTEMIS-1661:

Can you elaborate on your use-case and the severity of the need for this 
feature?  A past ancestor of the current broker implementation supported 
multiple configuration files, but there were complications which made the 
feature unattractive from a development perspective.  A single file is much 
simpler from a configuration, runtime, and development perspective.  

Also, it wouldn't be terribly difficult for users to use a templating engine, 
perl/bash script, etc. on their own to combine multiple snippets of 
configuration into a single broker.xml if their use-case requires it.  

> 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

Reply via email to