To be clear, if you're using the OpenWire or Qpid JMS client then broker
resources (i.e. addresses and queues) should be created with semantics that
match the kind of destination your client is using (e.g. queue or topic).
Justin
On Mon, Mar 1, 2021 at 11:30 AM Justin Bertram wrote:
> It's
It's possible you could write an interceptor [1] or perhaps a broker plugin
[2] to do what you want. Can you elaborate a bit on your use-case and why
you need this specifically?
Justin
[1]
http://activemq.apache.org/components/artemis/documentation/latest/intercepting-operations.html
[2]
Hello,
In Artemis, there are a few factors that decide what the routing-type of a
destination will be, I found:
*Using anycastPrefix/multicastPrefix on the acceptor
But that makes it a decision for the client
*Using default-address-routing-type on the address-settings
But this
