The virtual destination stuff is implemented on the broker, and it could be dynamic but would need some programatic support (extending the interceptor) to pick up changes at runtime.
The simple composite destination name syntax using a coma separated list works just fine and is dynamic. On 2 October 2012 18:02, exto <a...@middleware360.com> wrote: > With the setup you posted, looks like ActiveMQ would need to be restarted > each time we configure a composite destination. > > Does camel/activemq component support using composite destinations within > the camel endpoint uri similar to the following syntax: > http://activemq.apache.org/composite-destinations.html ? > > I suppose I could easily try, but since this thread has started already.. > ;-) > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/How-to-program-composite-queue-by-using-its-name-tp4657310p4657379.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://redhat.com http://blog.garytully.com
