You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2017/03/23 15:46:41 UTC

[jira] [Commented] (ARTEMIS-1065) Bring back in v2.0.x the API that allows clients to get the list of JMS Topics and Queue

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

Justin Bertram commented on ARTEMIS-1065:
-----------------------------------------

The broker no longer tracks JMS-specific artifacts like topics so it's not really possible to add this specific functionality back.  However, we can add some additional core management operations so you can identify the routing-type of a specific queue.

> Bring back in v2.0.x the API that allows clients to get the list of JMS Topics and Queue
> ----------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-1065
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1065
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.0.0
>            Reporter: Denis Forveille
>
> Artemis v1.5.x had an API to get the list of the Topics and Queues defined in the broker (From a JMS perpective) 
> This was implemented in class {{JMSServerControl}}, with methods {{getTopicNames()}} and {{getQueueNames()}}
> This class offered also many convenient methods ({{createTopic(..)}}...)
> This API has been dropped in v2.0.x and it does not seem to exist an easy way to get the list of Topics and Queues from a server/broker now.
> Please bring back the API to get the list of Topics and Queues from a JMS perspective from an Artemis v2.0.x server
> Thanks
> Discussion here:
> http://activemq.2283324.n4.nabble.com/Artemis-2-0-How-to-get-the-list-of-Queues-and-Topics-from-a-server-Fails-in-2-0-with-v1-5-3-code-td4724002.html



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