Mailing-List: contact users-help@qpid.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@qpid.apache.org
Received-SPF: pass (nike.apache.org: domain of gsim@redhat.com designates
 209.132.183.28 as permitted sender)
Message-ID: <4E2D78DF.2020409@redhat.com>
Date: Mon, 25 Jul 2011 15:08:31 +0100
From: Gordon Sim <gsim@redhat.com>
Organization: Red Hat UK Ltd, Registered in England and Wales under Company
 Registration No. 3798903, Directors: Michael Cunningham (USA), Mark Hegarty
 (Ireland), Matt Parsons (USA), Charlie Peters (USA)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.9.1.15) Gecko/20101027 Fedora/3.0.10-1.fc12 Lightning/1.0b1
 Thunderbird/3.0.10
MIME-Version: 1.0
To: users@qpid.apache.org
Subject: Re: issues migrating from qpid0.8 to qpid0.10
References: <1311598915.44949.YahooMailClassic@web114314.mail.gq1.yahoo.com>
In-Reply-To: <1311598915.44949.YahooMailClassic@web114314.mail.gq1.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 07/25/2011 02:01 PM, Nithesh Shetty wrote:
> This link does not provide any api to create exchange
> or assign an alternate exchange to a queue.

Read sections 2.4.3 and 2.16.

I'd also consider why you need to create exchanges and queues at runtime 
rather than have them preconfigured.

To create an exchange (direct exchange in this example):

'my-exchange; {create: always, node: {type: topic, x-declare:{type:direct}}'

To create a shared queue with a given alternate-exchange:

'my-queue; {create: always, 
node:{x-declare:{alternate-exchange:my-exchange}}}'

and to specify an alternate exchange on a subscription queue (bound to 
amq.topic with my-subject):

amq.topic/my-subject; {link:{x-declare:{alternate-exchange:my-exchange}}

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:users-subscribe@qpid.apache.org