Description
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.
Attachments
Issue Links
- is related to
-
AMQ-6088 Runtime configuration does not properly apply policy updates
-
- Resolved
-
-
AMQ-6035 Add an option to apply Virtual Destination changes immediately
-
- Resolved
-
- relates to
-
AMQ-4682 runtime configuration - allow selective application of changes to xml configuration without broker restart
-
- Resolved
-