[AMQ-5305] runtime configuration - allow changes to <destinations> configuration elements

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.10.0
• Fix Version/s: 5.11.0
• Component/s: Broker
• Assignee: Dejan Bosanac
• Reporter: Sam Wilkinson
• Created: 04/Aug/14 02:04
• Updated: 28/Aug/14 12:10
• Resolved: 28/Aug/14 12:10

Description

Extend the runtime configuration feature (AMQ-4682) to allow changes to the <destinations> configuration element.

As of 5.10.0 if you create a compositeTopic with queues/topics or filtered destinations within the <destinationInterceptors><virtualDestinationInterceptor><virtualDestinations> element the CompositeTopic will not showup in the Broker Manager Topics page.

<destinationInterceptors>
			<virtualDestinationInterceptor>
				<virtualDestinations>
					<!-- Add this compositeTopic after ActiveMQ start -->
					<compositeTopic name="CompositeTopic" forwardOnly="false">
						<forwardTo>
							<queue physicalName="ForwardedQueue" />
						</forwardTo>
					</compositeTopic>
				</virtualDestinations>
			</virtualDestinationInterceptor>
		</destinationInterceptors>
		<destinations>
			<!-- CompositeTopic and ForwardedQueue queue will not showup in the Broker Manager unless these are defined (or someone sends a message to the CompositeTopic. -->
			<!--<topic physicalName="CompositeTopic" />-->
			<!--<queue physicalName="ForwardedQueue" />-->
		</destinations>

Note: This is more just a usability/management improvement.
The broker does correctly forward messages to the ForwardedQueue, if it is not defined in the <destinations> element.