[jira] [Commented] (AMQ-5915) Support a Java API for the RuntimeConfigurationPlugin

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMQ-5915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14965123#comment-14965123 ] 

ASF subversion and git services commented on AMQ-5915:
------------------------------------------------------

Commit 43c3cae2c069c98215e2c0f1ff19e883fd6c0b86 in activemq's branch refs/heads/master from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=43c3cae ]

https://issues.apache.org/jira/browse/AMQ-5915

Adding a new JavaRuntimeConfigurationBroker which allows dynamic
changes to parts of the broker through a Java api instead of
just through xml configuration.  This is useful if starting a broker
with java config and not using xml.  It is also useful for temporary
changes that shouldn't be persisted.


> Support a Java API for the RuntimeConfigurationPlugin
> -----------------------------------------------------
>
>                 Key: AMQ-5915
>                 URL: https://issues.apache.org/jira/browse/AMQ-5915
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Broker
>            Reporter: Christopher L. Shannon
>            Assignee: Christopher L. Shannon
>             Fix For: 5.13.0
>
>
> Currently the RuntimeConfigurationPlugin supports modifying some parts of the broker at runtime by changing the xml configuration so the broker doesn't need to be restarted to pick up the changes.
> However, there are 2 issues with this approach.  First, in my situation I do not always use xml to configure the broker.  Many times a broker will be configured using Java (configuring a BrokerService directly) and I will store the configuration in a different way to manage this.  Second, I don't always want to permanently change the configuration.  Sometimes I need to temporarily create a new virtual destination for dynamic data flows but don't necessarily need to persist it in between restarts.
> Because of this, it would be useful in some cases to be able to make changes to the broker configuration using a Java API to programmatically do things such as modifying the virtual destinations.
> These changes would be temporary in nature as they wouldn't be persisted as they would be if xml was used.  However, if these changes need to be persisted the user could simply use xml to configure the broker or be responsible for storing this information however they want to recover after a restart of the broker.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)