INT-3512: Add <advice-chain> to the Aggregator
JIRA: https://jira.spring.io/browse/INT-3512 INT-3512: Fix typos INT-3512: add `expire-` prefix to the advice sub-elements INT-3512: Mark `AggregatorWithCustomReleaseStrategyTests` as `LONG_RUNNING_TEST` Doc Polishing
This commit is contained in:
committed by
Gary Russell
parent
113716effd
commit
d5f1bb6516
@@ -376,7 +376,10 @@ then you should simply provide an implementation of the <classname>ReleaseStrate
|
||||
group-timeout-expression="size() ge 2 ? 100 : -1" ]]><co id="aggxml21" linkends="aggxml21-txt" /><![CDATA[
|
||||
expire-groups-on-timeout="true" ]]><co id="aggxml22" linkends="aggxml22-txt" /><![CDATA[
|
||||
|
||||
scheduler="taskScheduler" /> ]]><co id="aggxml23" linkends="aggxml23-txt" /><![CDATA[
|
||||
scheduler="taskScheduler" > ]]><co id="aggxml23" linkends="aggxml23-txt" /><![CDATA[
|
||||
<expire-transactional/> ]]><co id="aggxml24" linkends="aggxml24-txt" /><![CDATA[
|
||||
<expire-advice-chain/> ]]><co id="aggxml25" linkends="aggxml25-txt" /><![CDATA[
|
||||
</aggregator>
|
||||
|
||||
<int:channel id="outputChannel"/>
|
||||
|
||||
@@ -610,6 +613,26 @@ then you should simply provide an implementation of the <classname>ReleaseStrate
|
||||
<code>group-timeout-expression</code> is not specified.
|
||||
</para>
|
||||
</callout>
|
||||
<callout arearefs="aggxml24" id="aggxml24-txt">
|
||||
<para>
|
||||
Since <emphasis>version 4.1</emphasis>. Allows a transaction to be started for the
|
||||
<code>forceComplete</code> operation. It is initiated from a
|
||||
<code>group-timeout(-expression)</code> or by a <classname>MessageGroupStoreReaper</classname> and
|
||||
is not applied to the normal <code>add/release/discard</code> operations. Only this sub-element or
|
||||
<code><expire-advice-chain/></code> is allowed.
|
||||
</para>
|
||||
</callout>
|
||||
<callout arearefs="aggxml25" id="aggxml25-txt">
|
||||
<para>
|
||||
Since <emphasis>version 4.1</emphasis>. Allows the configuration of any
|
||||
<interfacename>Advice</interfacename> for the
|
||||
<code>forceComplete</code> operation. It is initiated from a
|
||||
<code>group-timeout(-expression)</code> or by a <classname>MessageGroupStoreReaper</classname> and
|
||||
is not applied to the normal <code>add/release/discard</code> operations. Only this sub-element or
|
||||
<code><expire-transactional/></code> is allowed. A transaction <interfacename>Advice</interfacename>
|
||||
can also be configured here using the Spring <code>tx</code> namespace.
|
||||
</para>
|
||||
</callout>
|
||||
|
||||
</calloutlist>
|
||||
|
||||
|
||||
@@ -203,5 +203,14 @@
|
||||
See <xref linkend="async-gateway"/>.
|
||||
</para>
|
||||
</section>
|
||||
<section id="4.1-aggregator-advice-chain">
|
||||
<title>Aggregator Advice Chain</title>
|
||||
<para>
|
||||
<code>Aggregator</code>s and <code>Resequencer</code>s now support an
|
||||
<code><expire-advice-chain/></code> and <code><expire-transactional/></code> sub-elements
|
||||
to <emphasis>advise</emphasis> the <code>forceComplete</code> operation.
|
||||
See <xref linkend="aggregator-config"/> for more information.
|
||||
</para>
|
||||
</section>
|
||||
</section>
|
||||
</chapter>
|
||||
|
||||
Reference in New Issue
Block a user