Github user tabish121 commented on the issue:
https://github.com/apache/activemq-artemis/pull/1316
I'm in agreement with Robbie on this, I think the ease of which the
subscription names and "regular queue" names can collide should be avoided.
It's much easier to tell people (document) how to avoid this collision if we
have in place some means of at least making it something you couldn't do
without putting some deliberate effort into it or have some amazingly bad luck
on your side.
Lining up Core and AMQP mapping names for subscriptions seems like a good
thing to add to a 3.0 task list for changes that require a major version bump.
In the meantime if some configuration switch is added to control using one
naming scheme or another it ought to be added as an already deprecated sort of
thing that is going away in the next major version.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
