Subscription Wildcards Support? about stomp.py

[jasonrbriggs]

I believe that functionality would need to be supported by activemq. There's nothing specific in the stomp protocol (nor stomp.py) that I'm aware of to support wildcards.

[tseanard]

I had forgotten that I had logged this issue here, and had later solved the issue that I was having. Entering the solution here for others who may be looking to find it later.

On using wildcards to consume from ActiveMQ Queues using Stomp.py
The root of my issue was that I was not using a valid path separator. I was using the '/' character. Upon further review of the documentation, the '/' character could be the path separator, but the default path separator is actually the '.' character. After updating the naming of my queues in my application, I have been using Stomp.py with wildcards for several months in production. This wildcard support is something that is supported by ActiveMQ (when you do it right), and does not require anything special in STOMP.py or the stomp protocol - it's just that the queue that you subscribe to has a wild card in the string and ActiveMQ does what it needs to do.

• "/queue/test/q1" is a queue name that has a single path component
• ".queue.test.q1" is a queue name that has three path components

ActiveMQ Wildcard Reference: https://activemq.apache.org/wildcards

On Enumerating Queues Currently on the Broker
I was able to confirm that this just isn't a thing via the STOMP protocol. I believe (aka found but lost the reference) that there are ways to enumerate the queues via API calls, but I have not run them to ground because once I solved the wildcards challenge I no longer needed the queue enumeration.