From d2f3aa95a7e7f9a9552563d5e8e3319a6de6c8a1 Mon Sep 17 00:00:00 2001 From: Gary Russell Date: Thu, 17 Apr 2014 17:34:11 -0400 Subject: [PATCH] JMS Docbook Polishing Clarify the use of a `TemporaryQueue` with a `` only applies when no `reply-destination` is provided. --- src/reference/docbook/jms.xml | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/src/reference/docbook/jms.xml b/src/reference/docbook/jms.xml index 731cd6dd17..ec6836d305 100644 --- a/src/reference/docbook/jms.xml +++ b/src/reference/docbook/jms.xml @@ -274,7 +274,7 @@ JMS Message that is received as a reply and then converted into a Spring Integration Message to be subsequently sent to the 'reply-channel' as shown in the example configuration above. - <reply-listener/> + <reply-listener/> Spring Integration 2.2 introduced an alternative technique for handling replies. If you add a @@ -285,13 +285,15 @@ above. - When using a <reply-listener/>, instead of creating a TemporaryQueue + When using a <reply-listener/> with an outbound gateway with no + reply-destination, + instead of creating a TemporaryQueue for each request, a single TemporaryQueue is used (the gateway will create an additional TemporaryQueue, as necessary, if the connection to the broker is lost and recovered). - When using a correlation-key, multiple gateways can share the same + When using a correlation-key, multiple gateways can share the same reply destination because the listener container uses a selector that is unique to each gateway.