You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Martyn Taylor (JIRA)" <ji...@apache.org> on 2017/03/10 13:57:08 UTC

[jira] [Updated] (ARTEMIS-203) Investigate removal of namespaces for queues / topics

     [ https://issues.apache.org/jira/browse/ARTEMIS-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martyn Taylor updated ARTEMIS-203:
----------------------------------
    Fix Version/s:     (was: 2.0.0)
                   2.next

> Investigate removal of namespaces for queues / topics
> -----------------------------------------------------
>
>                 Key: ARTEMIS-203
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-203
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>    Affects Versions: 1.0.0, 1.1.0, 1.2.0
>            Reporter: Martyn Taylor
>             Fix For: 2.next
>
>
> We are currently using address name spacing on the broker to determine the    message producer client type, for example producing from a jms client results in messages being posted to jms.queue.*** where *** is the address provided by the client.  The has caused some confusions for users who were expecting to produce and consume to the same address using different clients.  
> This also has a couple of other consequences:
> 1. Messages can not be produced to the same queue by AMQP and JMS.
> 2. Consumers need to be aware of the producer client type so they can subscribe to the appropriately namespaced address.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)