INT-3499 AMQP Confirms/Returns Polishing
JIRA: https://jira.spring.io/browse/INT-3499 - Suppress (log) 'null' payload error when no correlation data - Change tests to use a dedicated template for confirms/returns Conflicts: spring-integration-amqp/src/test/java/org/springframework/integration/amqp/config/AmqpOutboundChannelAdapterParserTests.java src/reference/docbook/amqp.xml Resolved.
This commit is contained in:
@@ -471,10 +471,12 @@ public Object handle(@Payload String payload, @Header(AmqpHeaders.CHANNEL) Chann
|
||||
</callout>
|
||||
<callout arearefs="amqp-outbound-channel-adapter-xml-8-co" id="amqp-outbound-channel-adapter-xml-8">
|
||||
<para>An expression defining correlation data. When provided, this configures the underlying
|
||||
amqp template to receive publisher confirms. Requires a <classname>RabbitTemplate</classname> and a
|
||||
amqp template to receive publisher confirms. Requires a dedicated
|
||||
<classname>RabbitTemplate</classname> and a
|
||||
<classname>CachingConnectionFactory</classname> with the <code>publisherConfirms</code> property
|
||||
set to <code>true</code>. When a publisher confirm
|
||||
is received, it is written to either the confirm-ack-channel, or the confirm-nack-channel,
|
||||
is received, and correlation data is supplied,
|
||||
it is written to either the confirm-ack-channel, or the confirm-nack-channel,
|
||||
depending on the confirmation type. The payload of the confirm is the correlation data as
|
||||
defined by this expression and the message will have a header 'amqp_publishConfirm' set to
|
||||
true (ack) or false (nack). Examples: "headers['myCorrelationData']", "payload".
|
||||
@@ -497,8 +499,8 @@ public Object handle(@Payload String payload, @Header(AmqpHeaders.CHANNEL) Chann
|
||||
amqp_returnReplyText, amqp_returnExchange, amqp_returnRoutingKey</emphasis>.
|
||||
<emphasis>Optional</emphasis>.</para>
|
||||
<important>
|
||||
Using a <code>return-channel</code> requires a <classname>RabbitTemplate</classname> with either
|
||||
the <code>mandatory</code> or <code>immediate</code> properties set to <code>true</code>,
|
||||
Using a <code>return-channel</code> requires a <classname>RabbitTemplate</classname> with
|
||||
the <code>mandatory</code> property set to <code>true</code>,
|
||||
and a <classname>CachingConnectionFactory</classname>
|
||||
with the <code>publisherReturns</code> property set to <code>true</code>. When using multiple
|
||||
outbound endpoints with returns, a separate <classname>RabbitTemplate</classname> is needed
|
||||
@@ -585,8 +587,8 @@ public Object handle(@Payload String payload, @Header(AmqpHeaders.CHANNEL) Chann
|
||||
amqp_returnReplyText, amqp_returnExchange, amqp_returnRoutingKey</emphasis>.
|
||||
<emphasis>Optional</emphasis>.</para>
|
||||
<important>
|
||||
Using a <code>return-channel</code> requires a <classname>RabbitTemplate</classname> with either
|
||||
the <code>mandatory</code> or <code>immediate</code> properties set to <code>true</code>,
|
||||
Using a <code>return-channel</code> requires a <classname>RabbitTemplate</classname> with
|
||||
the <code>mandatory</code> property set to <code>true</code>,
|
||||
and a <classname>CachingConnectionFactory</classname>
|
||||
with the <code>publisherReturns</code> property set to <code>true</code>. When using multiple
|
||||
outbound endpoints with returns, a separate <classname>RabbitTemplate</classname> is needed
|
||||
|
||||
Reference in New Issue
Block a user