Re: enforcing routing-type question

[Justin Bertram <jb...@apache.org>]

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]
http://activemq.apache.org/components/artemis/documentation/latest/broker-plugins.html

On Wed, Feb 24, 2021 at 4:53 AM Dondorp, Erwin <er...@cgi.com>
wrote:

> 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 is only used "[...] if the broker is unable to determine the
> routing-type based on the client and/or protocol semantics [...]"
> in my tests using openwire/amqp, this did not help
>
> *        In the 'addresses' section
> But that only works for predefined concrete addresses, not for wildcards
>
> I'm looking for a way to set the routing-type in a strict way using only
> broker configuration; and still using autocreate/autodelete or any other
> address-settings.
> Any clues, hints, etc?
>
> thx,
> Erwin
>

Re: enforcing routing-type question

[Justin Bertram <jb...@apache.org>]

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 <jb...@apache.org> wrote:

> 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]
> http://activemq.apache.org/components/artemis/documentation/latest/broker-plugins.html
>
> On Wed, Feb 24, 2021 at 4:53 AM Dondorp, Erwin <er...@cgi.com>
> wrote:
>
>> 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 is only used "[...] if the broker is unable to determine the
>> routing-type based on the client and/or protocol semantics [...]"
>> in my tests using openwire/amqp, this did not help
>>
>> *        In the 'addresses' section
>> But that only works for predefined concrete addresses, not for wildcards
>>
>> I'm looking for a way to set the routing-type in a strict way using only
>> broker configuration; and still using autocreate/autodelete or any other
>> address-settings.
>> Any clues, hints, etc?
>>
>> thx,
>> Erwin
>>
>