Spring/spring-ws
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

SWS-255

Browse Source
This commit is contained in:
Arjen Poutsma
2007-12-18 19:10:12 +00:00
parent 9376403f02
commit 2d34abe163
1 changed files with 11 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
src/docbkx/client.xml
View File

@@ -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>