Github user rlodge commented on the issue:
https://github.com/apache/activemq-artemis/pull/875
@mtaylor What I'm hearing is that basically, following changes in 780, a
client would be able to send to an address "RecordUpdateNotifications", other
clients could subscribe to
"RecordUpdateNotifications::SystemARecordUpdateNotifications" and it would act
essentially like virtual topics do now; all "RecordUpdateNotifications::*"
subscriptions would read from queues coming from the single address?
If so, do OpenWire clients need to use a specific queue / address naming
scheme, or would it happen automatically somehow (and could it be mapped from
the VirtualTopic.* naming scheme)? It's not a terribly large problem for us to
go through and change our queues from VirtualTopic.* to a slightly different
naming scheme, though we'd rather change nothing about the clients; it would be
more difficult to somehow change the API's we were calling...
---
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.
---
