You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (Jira)" <ji...@apache.org> on 2022/09/14 16:22:00 UTC

[jira] [Resolved] (ARTEMIS-2303) Override properties in broker.xml with file or map

     [ https://issues.apache.org/jira/browse/ARTEMIS-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram resolved ARTEMIS-2303.
-------------------------------------
    Resolution: Duplicate

> 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
(v8.20.10#820010)