INT-1875 added documentation about JMS Header Mapper
This commit is contained in:
@@ -201,6 +201,24 @@
|
|||||||
Message to be subsequently sent to the 'reply-channel' as shown in the example configuration above.
|
Message to be subsequently sent to the 'reply-channel' as shown in the example configuration above.
|
||||||
</para>
|
</para>
|
||||||
</section>
|
</section>
|
||||||
|
|
||||||
|
<section id="jms-header-mapping">
|
||||||
|
<title>Mapping Message Headers to/from JMS Message</title>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
JMS Message can contain meta-information such as JMS API headers as well as simple properties.
|
||||||
|
You can map those to/from Spring Integration Message Headers using <classname>JmsHeaderMapper</classname>.
|
||||||
|
The JMS API headers are passed to the appropriate setter methods (e.g. setJMSReplyTo) whereas other headers will
|
||||||
|
be copied to the general properties of the JMS Message.
|
||||||
|
|
||||||
|
JMS Outbound Gateway is bootstrapped with the default implementation of JmsHeaderMapper which will map
|
||||||
|
standard JMS API Headers as well as primitive/String Message Headers. Custom header mapper could also be
|
||||||
|
provided via <code>header-mapper</code> attribute of inbound and outbound gateways.
|
||||||
|
</para>
|
||||||
|
|
||||||
|
</section>
|
||||||
|
|
||||||
|
|
||||||
<section id="jms-conversion-and-marshalling">
|
<section id="jms-conversion-and-marshalling">
|
||||||
<title>Message Conversion, Marshalling and Unmarshalling</title>
|
<title>Message Conversion, Marshalling and Unmarshalling</title>
|
||||||
<para>
|
<para>
|
||||||
|
|||||||
@@ -557,6 +557,9 @@
|
|||||||
<tool:annotation kind="ref">
|
<tool:annotation kind="ref">
|
||||||
<tool:expected-type type="org.springframework.integration.jms.JmsHeaderMapper"/>
|
<tool:expected-type type="org.springframework.integration.jms.JmsHeaderMapper"/>
|
||||||
</tool:annotation>
|
</tool:annotation>
|
||||||
|
<xsd:documentation>
|
||||||
|
Allows to specify custom implementation of JmsHeaderMapper to map Message Headers to JMS Message.
|
||||||
|
</xsd:documentation>
|
||||||
</xsd:appinfo>
|
</xsd:appinfo>
|
||||||
</xsd:annotation>
|
</xsd:annotation>
|
||||||
</xsd:attribute>
|
</xsd:attribute>
|
||||||
@@ -740,6 +743,9 @@
|
|||||||
<tool:annotation kind="ref">
|
<tool:annotation kind="ref">
|
||||||
<tool:expected-type type="org.springframework.integration.jms.JmsHeaderMapper"/>
|
<tool:expected-type type="org.springframework.integration.jms.JmsHeaderMapper"/>
|
||||||
</tool:annotation>
|
</tool:annotation>
|
||||||
|
<xsd:documentation>
|
||||||
|
Allows to specify custom implementation of JmsHeaderMapper to map Message Headers to JMS Message.
|
||||||
|
</xsd:documentation>
|
||||||
</xsd:appinfo>
|
</xsd:appinfo>
|
||||||
</xsd:annotation>
|
</xsd:annotation>
|
||||||
</xsd:attribute>
|
</xsd:attribute>
|
||||||
|
|||||||
Reference in New Issue
Block a user