[
https://issues.apache.org/jira/browse/ARTEMIS-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15956811#comment-15956811
]
ASF GitHub Bot commented on ARTEMIS-1093:
-----------------------------------------
Github user gaohoward commented on the issue:
https://github.com/apache/activemq-artemis/pull/1172
Yes OpenWire still referring to the queue name, in JMS terms. Not sure what
you meant by "ANYCAST address name". My understanding is that when you send
messages you send to an address of anycast and/or multicast route type, is that
correct?
> Full qualified queue name support
> ---------------------------------
>
> Key: ARTEMIS-1093
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1093
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.0.0
> Reporter: Howard Gao
> Assignee: Howard Gao
> Fix For: 2.next
>
>
> Broker should support full qualified queue names (FQQN) as well as bare queue
> names. This means when clients access to a queue they have two equivalent
> ways to do so. One way is by queue names and the other is by FQQN (i.e.
> address::qname) names. When accessing a queue by its bare name, it is
> required that the name should be unique across all addresses.
> Otherwise a warning is given and client should use FQQN instead.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
