File tree Expand file tree Collapse file tree 1 file changed +11
-1
lines changed
Expand file tree Collapse file tree 1 file changed +11
-1
lines changed Original file line number Diff line number Diff line change 9999 For sending messages over JMS, Spring Web Services provides the
100100 <classname >JmsMessageSender</classname >. This class uses the facilities of the Spring framework
101101 to transform the <interfacename >WebServiceMessage</interfacename > into a JMS
102- <interfacename >BytesMessages </interfacename >, send it on its way on a
102+ <interfacename >Message </interfacename >, send it on its way on a
103103 <interfacename >Queue</interfacename > or <interfacename >Topic</interfacename >, and receive a
104104 response (if any).
105105 </para >
113113 For more information on this URI syntax, refer to the class level Javadocs of the
114114 <classname >JmsMessageSender</classname >.
115115 </para >
116+ <para >
117+ By default, the <classname >JmsMessageSender</classname > send JMS
118+ <interfacename >BytesMessage</interfacename >, but
119+ this can be overriden to use <interfacename >TextMessages</interfacename > by using the
120+ <literal >messageType</literal > parameter on the JMS URI. For example:
121+ <uri >jms:Queue?messageType=TEXT_MESSAGE</uri >.
122+ Note that <interfacename >BytesMessages</interfacename > are the prefered type, because
123+ <interfacename >TextMessages</interfacename > do not support attachments and charactering
124+ encodings reliably.
125+ </para >
116126 <para >
117127 The following example shows how to use the JMS transport in combination with an ActiceMQ
118128 connection factory:<programlisting ><![CDATA[ <beans>
You can’t perform that action at this time.
0 commit comments