I believe that listing all virtual topics in the staticallyIncludedDestinations element would work. Please let us know if it works, so that the next person knows whether this is an option for them.
Tim On Oct 14, 2016 9:07 PM, "Devlin" <rbasmaj...@ofiglobal.com> wrote: > Tim, > > The documentation on this topic (haha!) was never 100% clear to me. Here's > what we want to achieve given our architecture: > > Topology > -------- > 12 broker network (full-mesh) > All destinations dynamic (no static definitions) > Clients connect and reconnect with random brokers (preference to local) > AMQ 6.2.1 (preping for 6.3) > > What we need > --------------- > + Virtual topics working in above architecture. > * Virtual topics to support queue *and* normal topic subscribers (can live > without this if duplication cannot be avoided) > > It's my understanding AMQ 6.3 still uses ActiveMQ 5.11, bummer if that's > true, so as you said, we can't use useVirtualDestSubs broker params. > > Question > -------- > If we statically-defined all virtual topics (we don't have many), can we > meet the requirements above? > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/Virtual-topics-custom-prefix-limitations-tp4717481p4717957.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
