Return-Path: 
 <dev-return-34468-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org>
X-Original-To: apmail-activemq-dev-archive@www.apache.org
Delivered-To: apmail-activemq-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id C2416D28E
	for <apmail-activemq-dev-archive@www.apache.org>;
 Tue,  6 Nov 2012 16:50:14 +0000 (UTC)
Received: (qmail 31419 invoked by uid 500); 6 Nov 2012 16:50:14 -0000
Delivered-To: apmail-activemq-dev-archive@activemq.apache.org
Received: (qmail 31073 invoked by uid 500); 6 Nov 2012 16:50:13 -0000
Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@activemq.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@activemq.apache.org>
List-Post: <mailto:dev@activemq.apache.org>
List-Id: <dev.activemq.apache.org>
Reply-To: dev@activemq.apache.org
Delivered-To: mailing list dev@activemq.apache.org
Received: (qmail 30655 invoked by uid 99); 6 Nov 2012 16:50:12 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Nov 2012 16:50:12 +0000
Date: Tue, 6 Nov 2012 16:50:12 +0000 (UTC)
From: "Gary Tully (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <666704201.75069.1352220612509.JavaMail.jiratomcat@arcas>
In-Reply-To: <106893432.74965.1352218812509.JavaMail.jiratomcat@arcas>
Subject: [jira] [Resolved] (AMQ-4162) Provide JMX visibility into options
 applied via destination name query parameters
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

Gary Tully resolved AMQ-4162.
-----------------------------

    Resolution: Fixed
      Assignee: Gary Tully

in http://svn.apache.org/viewvc?rev=1406210&view=rev

options now exposed by destinationView, queues and topics
                
> Provide JMX visibility into options applied via destination name query parameters
> ---------------------------------------------------------------------------------
>
>                 Key: AMQ-4162
>                 URL: https://issues.apache.org/jira/browse/AMQ-4162
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Broker, JMX
>    Affects Versions: 5.7.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>              Labels: destinations, jmx, metadata
>             Fix For: 5.8.0
>
>
> Users would like to be able to add meta information to a destination, such as the owner of a queue.
> Destination options allow arbitrary information to be associated with a destination via a query parameter on the name.
> They are normally hidden b/c they are interpreted internally as policy entry overrides so not generally of interest.
> Providing visibility of this information makes it usable for meta info purposes b/c a user can add any information they like in there.
> {code}
>  <broker ...>
>    <destinations>
>      <queue physicalName="FOO.BAR?owner=joe&mobile=123" />
>    </destinations>
>  </broker>{code}
> via JMX the query string is available in the DestinationView via the options attribute.
> Changing this information over time does not effect the destination.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira