Hi Justin, thanks for the response!
My current solution is to mark the messages at the publisher side as "for
app 1", "for app 2" etc, which kinda defeats the purpose of the publisher
being agnostic to subscribers.
Perhaps there's another way?
Thanks again,
Adi
--
Sent from: http://activemq.228
In Artemis when a JMS consumer creates a subscription on a topic it creates
a queue on the broker. If the subscription has a selector then the queue
on the broker is created with a corresponding "filter". The filter on a
queue is immutable so there's no way to change the subscription's
selector.