Thanks so much for the help!!!   In this case, it is preferred to receive the 
messages all on one queue.  When all the other clients have been updated, then 
I can go back to the basic queue creation string.  For now just looking for one 
inbound queue on the server.  

Thanks again for the help!!!



On 2011-06-03, at 15:19, Ted Ross <[email protected]> wrote:

> Just to be clear, this address causes all messages sent to 
> "amq.direct/my_routing_key" to be enqueued on "my_queue".
> 
> If you don't want those messages placed on "my_queue", you can create two 
> receivers.  One with "my_queue;{create: always}" and the other with 
> "amq.direct/my_routing_key".  You can then use Session.nextReceiver() to wait 
> for the next receiver to have an available message.
> 
> -Ted
> 
> 
> On 06/03/2011 02:29 PM, Virgilio Alexandre Fornazin wrote:
>> You have to include the x-bindings like the following syntax
>> 
>> my_queue ; { mode: consume, create: always, node: { type: queue, x-bindings:
>> [{ exchange: amq.direct, queue: my_queue, key: my_routing_key }] } }
>> 
>> -----Original Message-----
>> From: Phil Brown [mailto:[email protected]]
>> Sent: sexta-feira, 3 de junho de 2011 15:25
>> To: [email protected]
>> Subject: address strings
>> 
>> Hi,
>> 
>> I am having an issue with address strings.  About 1/2 of the client
>> applications are still using the qpid client api and the rest are using qpid
>> messaging api.  It isn't quite feasible to change the older apps at this
>> particular instance.
>> 
>> The server creates a queue using the messaging api:
>> 
>> session.CreateReceiver("my_queue; {create: always}";
>> 
>> The older clients are declaring the "my_queue" using routing key
>> "my_routing_key"  and sending messages via "amq.direct/my_routing_key".
>> 
>> Is there a way to declare my server's receiver address such that it will
>> handle messages sent either directly to the queue or via
>> "amq.direct/my_routing_key"?
>> 
>> Thanks so much for you time and help!
>> 
>>       Phil.
>> 
>> 
>> ---------------------------------------------------------------------
>> Apache Qpid - AMQP Messaging Implementation
>> Project:      http://qpid.apache.org
>> Use/Interact: mailto:[email protected]
>> 
> 
> 
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:[email protected]
> 

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]

Reply via email to