[AMQ-4682] runtime configuration - allow selective application of changes to xml configuration without broker restart

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.8.0
• Fix Version/s: 5.9.0
• Component/s: Broker
• Labels: configuration runtime updates
• Assignee: Gary Tully
• Reporter: Gary Tully
• Created: 14/Aug/13 13:18
• Updated: 07/Aug/15 13:05
• Resolved: 03/Sep/13 11:51

Description

support on the fly configuration changes where appropriate.
Via JMX it is possible to make changes but they don't persist.
Via osgi we can restart the broker to pick up changes to xml config
but where it makes sense, we should be able to apply changes on the fly.

A first example would be the addition on a new network connector by
the addition of the relevant xml config (edit or copy over) that is
in use by the broker.

Issue Links

• breaks: AMQ-4702 Error resolving org.jvnet.jaxb2_commons packages
• is related to: AMQ-4642 regression: SpringSslContext no longer supports classpath:filename syntax for referencing files
• is related to: AMQ-5915 Support a Java API for the RuntimeConfigurationPlugin
• relates to: AMQ-4738 Expose JMX operation to create composite destinations at runtime