Github user mtaylor commented on the issue:
https://github.com/apache/activemq-artemis/pull/1775
A lot of discussion here :). This should not override what the client
requests. There are a couple of ways addresses and queues can be set up in
Artemis.
The first way is to do what @michaelandrepearce has described. The client
is explicit about what it wants. Typical example is JMS where the spec is very
specific. In this case the client passes a description of what it wants to the
broker. If the client requests a durable subscription, or similar then the
broker will try to serve that request. Providing the client has the correct
security permissions and address settings it's all good.
The second way is for the broker to decide how to handle things. This can
either be configured by being very specific about what resources can exist on
the broker, for example, locking down all the addresses and pre-creating all
queues and turning off any create permissions or auto-create settings or it can
be configured to be open and auto-create things that aren't specified. This
setting is for this 2nd case. With something like AMQP or STOMP the clients
don't need to be aware of what type of resource they're sending or receiving
from. They only require an address to subscribe from or send to. If the
address the client asks for does not yet exist, the broker can create it
automatically. This is what these auto-create settings are used for. They
should not conflict with what clients ask for.
---
