[
https://issues.apache.org/jira/browse/ARTEMIS-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668333#comment-15668333
]
ASF GitHub Bot commented on ARTEMIS-851:
----------------------------------------
Github user clebertsuconic commented on the issue:
https://github.com/apache/activemq-artemis/pull/888
I have come across the need to eventually replace configuration.xml
properties using System.properties. This is useful for embedded cases, although
the specific need was for use cases where the XML couldn't be changed on a
specific case within Wildfly embedded.
Instead of dealing with specific cases, I have come with a simple
implementation that will use Bean Utils and populate the Configuration with the
properties.
> Parse System.properties as Configuration
> ----------------------------------------
>
> Key: ARTEMIS-851
> URL: https://issues.apache.org/jira/browse/ARTEMIS-851
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Affects Versions: 1.5.0
> Reporter: clebert suconic
> Assignee: clebert suconic
> Fix For: 1.6.0
>
>
> When adding new properties to the configuration, some times users can't
> change their configuration and would only be able to add stuff through
> system.properties.
> I'm adding a new enhancement where System properties with a given prefix will
> be set through BeanUtils on the configuration.
> The System property will always replace whatever was defined within the XML,
> which will also be useful to eventually change behaviours for temporary tests.
> I am planning to also log.info on replaced properties...
> The prefix will be configurable, with the default being brokerconfig.
> That way you will have:
> For example: if you want to configure FailbackDelay on the configuration with
> a system property you would do:
> -Dbrokerconfig.failbackDelay=5000
> There will be a property configuration where users can change the prefix.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
