From 4a9a63129b25b7e5cac4dcb17c4af0382b29094b Mon Sep 17 00:00:00 2001
From: Mark Fisher <markfisher@vmware.com>
Date: Tue, 16 Nov 2010 09:42:45 -0500
Subject: [PATCH] INT-1625 updated docs for the 'error-channel' attribute on
 JMS 'message-driven-channel-adapter'

---
 docs/src/reference/docbook/jms.xml | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/docs/src/reference/docbook/jms.xml b/docs/src/reference/docbook/jms.xml
index ac64c5b8f4..e301569c87 100644
--- a/docs/src/reference/docbook/jms.xml
+++ b/docs/src/reference/docbook/jms.xml
@@ -83,6 +83,18 @@
       be passed along to the <interfacename>MessageChannel</interfacename> as soon as they are received from the underlying
       JMS consumer.
     </para>
+    <para>Finally, the &lt;message-driven-channel-adapter&gt; also accepts the 'error-channel' attribute. This
+      provides the same basic functionality as described in <xref linkend="gateway-proxy"/>.
+<programlisting language="xml"><![CDATA[ <jms:message-driven-channel-adapter id="jmsIn" destination="inQueue" 
+         channel="exampleChannel"
+         error-channel="exampleErrorChannel"/>
+]]></programlisting>
+	      When comparing this to the generic gateway configuration, or the JMS 'inbound-gateway' that will
+          be discussed below, the key difference here is that we are in a one-way flow
+          since this is a 'channel-adapter', not a gateway. Therefore, the flow downstream from the
+          'error-channel' should also be one-way. For example, it could simply send to a logging handler,
+          or it could be connected to a different JMS &lt;outbound-channel-adapter&gt; element.
+	  </section>
   </section>
 
   <section id="jms-outbound-channel-adapter">