[
https://issues.apache.org/jira/browse/ARTEMIS-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905181#comment-15905181
]
Martyn Taylor commented on ARTEMIS-550:
---------------------------------------
There will be differences in the configuration.
If you use the Artemis scheme i.e. FQQN, you don't need to configure anything.
You probably want to lock down the broker using security settings but actually
out of the box, you can do the main thing that virtual topics offers you,
shared subscriptions, queue control etc...
We do also want to ensure that users migrating to Artemis from ActiveMQ 5.x
have an appropriate migration path. Part of that is adding the ability to
support the ActiveMQ 5.x virtual topic naming scheme, so that users do not have
to update client applications. There will be a way to do this though it may be
more than 1 line in the configuration.
I've changed the JIRA to not include OpenWire (it's in fact a issue that should
be resolved across all protocols). If you could add specific examples of what
you require to the JIRA we can address them when we come to implementing the
features.
Cheers
> Add support for virtual topic consumers
> ---------------------------------------
>
> Key: ARTEMIS-550
> URL: https://issues.apache.org/jira/browse/ARTEMIS-550
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 1.3.0
> Reporter: Benjamin Graf
> Assignee: Martyn Taylor
>
> Artemis should support virtual topic consumers as alternative to topic
> subscriptions as ActiveMQ itself does.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
