activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-1093) Full qualified queue name support
Date Wed, 12 Apr 2017 09:00:50 GMT

    [ https://issues.apache.org/jira/browse/ARTEMIS-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15965574#comment-15965574
] 

ASF subversion and git services commented on ARTEMIS-1093:
----------------------------------------------------------

Commit a9a3c478089ac0f5d32fd414e45441a340dbeb5d in activemq-artemis's branch refs/heads/master
from [~gaohoward]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=a9a3c47 ]

ARTEMIS-1093 Full qualified queue name support

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. Currently only receiving is supported.


> 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)

Mime
View raw message