[
https://issues.apache.org/jira/browse/ARTEMIS-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16437558#comment-16437558
]
Justin Bertram commented on ARTEMIS-1802:
-----------------------------------------
bq. Regarding naming, the bindings seem to be an internal thing and not
something a user should know and worry about, as opposed to diverts and queues
that are named and defined in the broker configuration file. Would it make
sense to lift this naming restriction to better hide the internal
implementation?
I think that's reasonable.
However, this may be moot for your use-case if we can work out ARTEMIS-1794.
> Cannot use the same name for a divert and an address
> ----------------------------------------------------
>
> Key: ARTEMIS-1802
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1802
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.5.0
> Reporter: Lionel Cons
> Priority: Major
>
> I'm trying to use diverts to emulate ActiveMQ 5's virtual destinations
> (http://activemq.apache.org/virtual-destinations.html). The use case is a
> single topic ({{foo}}) bound to two queues ({{foo-test}} and {{foo-prod}}).
> The following configuration snippet almost works:
> {code:xml}
> <addresses>
> <!-- the receiving topic "foo" -->
> <address name="foo">
> <multicast/>
> </address>
> <!-- the backend queue "test" -->
> <address name="foo-test">
> <anycast>
> <queue name="foo-test"/>
> </anycast>
> </address>
> <!-- the backend queue "prod" -->
> <address name="foo-prod">
> <anycast>
> <queue name="foo-prod"/>
> </anycast>
> </address>
> ...
> </addresses>
> <diverts>
> <!-- the divert to copy from "foo" to "foo-test" -->
> <divert name="foo-test">
> <address>foo</address>
> <forwarding-address>foo-test</forwarding-address>
> <exclusive>false</exclusive>
> </divert>
> <!-- the divert to copy from "foo" to "foo-prod" -->
> <divert name="foo-prod">
> <address>foo</address>
> <forwarding-address>foo-prod</forwarding-address>
> <exclusive>false</exclusive>
> </divert>
> </diverts>
> {code}
> Artemis give me an error:
> {code}
> AMQ222006: Binding already exists with name foo-test, divert will not be
> deployed
> {code}
> Changing the divert names fixes the problem.
> Why can't I use the same name both for the queue and the divert feeding the
> queue?
> Since these are different kinds of objects, I should be able to reuse the
> same name, shouldn't I?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
