[
https://issues.apache.org/jira/browse/ARTEMIS-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825627#comment-16825627
]
Justin Bertram commented on ARTEMIS-2303:
-----------------------------------------
For embedded brokers and unit tests why can't you simply call
{{System.setProperty()}} or {{System.setProperties()}}? With the former you can
set individual properties, and with the latter you can use a {{Properties}}
instance (which can be easily initialized from a file using the {{load()}}
method).
> Override properties in broker.xml with file or map
> --------------------------------------------------
>
> Key: ARTEMIS-2303
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2303
> Project: ActiveMQ Artemis
> Issue Type: Wish
> Components: Broker
> Affects Versions: 2.7.0
> Reporter: SL
> Priority: Minor
>
> Currently, Artemis can use system properties to substitute values in
> broker.xml.
> It would be nice if there was a mean to fetch the properties from a file OR a
> {{Properties}} instance instead, for embedded brokers and unit tests.
> Actually, the properties are set via
> {code:java|title=ConfigurationImpl.java}
> @Override
> public Configuration parseSystemProperties() throws Exception {
> parseSystemProperties(System.getProperties());
> return this;
> }
> {code}
> which is called from {{parse(...)}} and {{internalStart()}} ; there should be
> a way to feed explicitly the properties from the upper layers.
> This is sort-of a regression from AMQ5 which inherited some flexibility from
> its spring configuration in those cases.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
