From f14a0c26e2495c8f70299f45692eb2717aa86227 Mon Sep 17 00:00:00 2001
From: Chris Beams <cbeams@vmware.com>
Date: Sat, 7 Aug 2010 13:57:09 +0000
Subject: [PATCH] Distinguish JMS remoting from JMS messaging support
 (SPR-7339)

git-svn-id: https://src.springframework.org/svn/spring-framework/trunk@3531 50f2f4bb-b051-0410-bef5-90022cba6387
---
 spring-framework-reference/src/remoting.xml | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/spring-framework-reference/src/remoting.xml b/spring-framework-reference/src/remoting.xml
index 9603443588f..5c916eb8d5f 100644
--- a/spring-framework-reference/src/remoting.xml
+++ b/spring-framework-reference/src/remoting.xml
@@ -1063,7 +1063,11 @@ public class AccountServiceEndpoint {
     Spring Framework is pretty basic - it sends and receives on the
     <interfacename>same thread</interfacename> and in the <emphasis>same
     non-transactional</emphasis> <interfacename>Session</interfacename>, and
-    as such throughput will be very implementation dependent.</para>
+    as such throughput will be very implementation dependent. Note that
+    these single-threaded and non-transactional constraints apply only to
+    Spring's JMS <emphasis role="bold">remoting</emphasis> support. See
+    <xref linkend="jms"/> for information on Spring's rich support for
+    JMS-based <emphasis role="bold">messaging</emphasis>.</para>
 
     <para>The following interface is used on both the server and the client
     side.</para>