Github user jbertram commented on the issue: https://github.com/apache/activemq-artemis/pull/701 There's no way to eliminate the user's need to understand how non-core protocols map to the core implementation. We have addresses and queues and just about all the configuration and management details relate to those two resources. Also, a "subscription" isn't really a core idea. In core, a "subscription" is just a queue. Core and JMS clients can already "share" queues. I understand the need for users to control access to individual queues which are mapped to the same address (which is what this PR is meant to address). I don't understand the whole "shared subscription" use-case.
--- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---