Hi,
Just a note that we have discovered that adding a CompositeDestination
*removes* the default configuration for VirtualTopics, and the example
given in VirtualTopic documentation does not match the defaults.
It would be helpful for future users if the documentation for
CompositeDestination included a warning that using them will disable
default behaviour for VirtualTopics, and the VirtualTopic documentation
included a config for the default behaviour.
<destinationInterceptors>
<virtualDestinationInterceptor>
<virtualDestinations>
<compositeTopic name="PUBLISH_TOPIC" forwardOnly="false">
<forwardTo>
<queue physicalName="PUBLISH" />
<topic physicalName="ETLPUBLISH" />
</forwardTo>
</compositeTopic>
<virtualTopic name="VirtualTopic.>" prefix="Consumer.*."
selectorAware="false"/>
</virtualDestinations> </virtualDestinationInterceptor>
</destinationInterceptors>
