From 89f0b9c7020627b02c03c71beb2f4e094e9f98bc Mon Sep 17 00:00:00 2001
From: Gary Russell <grussell@vmware.com>
Date: Tue, 3 Jul 2012 11:11:26 -0400
Subject: [PATCH] AMQP-247 Queue ID/Name Documentation

Add a tip explaining when to use ID Vs. name when
defining a <queue/>.
---
 src/reference/docbook/amqp.xml | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/src/reference/docbook/amqp.xml b/src/reference/docbook/amqp.xml
index 8817fcaf..ef7d9411 100644
--- a/src/reference/docbook/amqp.xml
+++ b/src/reference/docbook/amqp.xml
@@ -803,6 +803,14 @@ Object receiveAndConvert(String queueName) throws AmqpException;]]></programlist
 
     <programlisting><![CDATA[<rabbit:queue name="stocks.trade.queue"/>]]></programlisting>
 
+	<tip>
+		You can provide both an <emphasis>id</emphasis> and a <emphasis>name</emphasis> attribute.
+		This allows you to refer to the queue (for example in a binding) by an id that is
+		independent of the queue name. It also allows standard Spring features such as
+		property placeholders, and SpEL expressions for the queue name; these features
+		are not available when using the name as the bean identifier.
+	</tip>
+	
 	<para>Queues can be configured with additional arguments, for example,
 	'x-message-ttl' or 'x-ha-policy'. Using the namespace support, they are provided in the form of
 	a Map of argument name/argument value pairs, using the