Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of tabish121@gmail.com
 designates 209.85.216.54 as permitted sender)
Message-ID: <1357691790.2732.2.camel@OfficePC>
Subject: Re: Query related to CMS API createQueue
From: Timothy Bish <tabish121@gmail.com>
To: users@activemq.apache.org
Date: Tue, 08 Jan 2013 19:36:30 -0500
In-Reply-To: <1357691368393-4661517.post@n4.nabble.com>
References: <1357691368393-4661517.post@n4.nabble.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0

On Tue, 2013-01-08 at 16:29 -0800, Gangadhar Rao wrote: 
> Is there any way we can have the createQueue CMS API to throw an error if the
> particular queue
> is not present on the broker rather than creating a new one.
> 
> 

Nope, the createQueue / createTopic methods don't interact with the
broker.  You can look into the security model of AMQ as that's how you
would restrict users from dynamically creating destinations, see:

http://activemq.apache.org/how-do-i-create-new-destinations.html

and 

http://activemq.apache.org/security.html

This would cause an error to be thrown upon consumer or producer
creation if no destination exists and the user is not permitted to
create it.

> 
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Query-related-to-CMS-API-createQueue-tp4661517.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.

-- 
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.bish@redhat.com | www.fusesource.com | www.redhat.com 
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/