From 2d34abe163ae6d2d6d120ba72e838c45ad0693fa Mon Sep 17 00:00:00 2001
From: Arjen Poutsma <apoutsma@vmware.com>
Date: Tue, 18 Dec 2007 19:10:12 +0000
Subject: [PATCH] SWS-255

---
 src/docbkx/client.xml | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/src/docbkx/client.xml b/src/docbkx/client.xml
index 9cbd4f74..b9b18f51 100644
--- a/src/docbkx/client.xml
+++ b/src/docbkx/client.xml
@@ -99,7 +99,7 @@
                         For sending messages over JMS, Spring Web Services provides the
                         <classname>JmsMessageSender</classname>. This class uses the facilities of the Spring framework
                         to transform the <interfacename>WebServiceMessage</interfacename> into a JMS
-                        <interfacename>BytesMessages</interfacename>, send it on its way on a
+                        <interfacename>Message</interfacename>, send it on its way on a
                         <interfacename>Queue</interfacename> or <interfacename>Topic</interfacename>, and receive a
                         response (if any).
                     </para>
@@ -113,6 +113,16 @@
                         For more information on this URI syntax, refer to the class level Javadocs of the
                         <classname>JmsMessageSender</classname>.
                     </para>
+                    <para>
+                        By default, the <classname>JmsMessageSender</classname> send JMS
+                        <interfacename>BytesMessage</interfacename>, but
+                        this can be overriden to use <interfacename>TextMessages</interfacename> by using the
+                        <literal>messageType</literal> parameter on the JMS URI. For example:
+                        <uri>jms:Queue?messageType=TEXT_MESSAGE</uri>.
+                        Note that <interfacename>BytesMessages</interfacename> are the prefered type, because 
+                        <interfacename>TextMessages</interfacename> do not support attachments and charactering
+                        encodings reliably.
+                    </para>
                     <para>
                         The following example shows how to use the JMS transport in combination with an ActiceMQ
                         connection factory:<programlisting><![CDATA[<beans>