I have yet to find a use case for conduitSubscriptions=false for topics. I think it may make sense to make the conduitSubscriptions flag applicable to queues only and always conduit for topics. A quick (but not foolproof) validation would be a full test run with the change to see if there is a use case encoded in a test some where.
With temp destinations, filtering is not an option as the name of a temp destination is auto generated from the auto generated connection id. There is no know string to filter on unless the client app uses non standard apis to specify the temp dest name. On 13 January 2011 01:01, adam <adam.suss...@gmail.com> wrote: > > Alternatively,the only reason we have to have two different networkConnectors > right now is so that we can vary the settings of conduitSubscriptions for > queues vs topics. Is there maybe a way we could rework that configuration > so that we can have different conduitSubscription settings for each kind of > destination on a single network connection? > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Duplicate-messages-on-temporary-Topics-tp3209648p3215057.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- http://blog.garytully.com http://fusesource.com
