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

polishing

Browse Source
This commit is contained in:
Mark Fisher
2011-09-19 14:35:31 -04:00
parent 779dc39673
commit 776159bfec
3 changed files with 18 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/src/reference/docbook/aggregator.xml
View File

@@ -398,13 +398,14 @@ then you should simply provide an implementation of the <classname>ReleaseStrate
<callout arearefs="aggxml08">
<para>
Indicates that partially aggregated messages should be sent to the 'output-channel' or 'replyChannel'
once the particular <classname>MessageGroup</classname> had expired (see <code>MessageGroupStore.expireMessageGroups(long)</code>). One of the ways of expiring <classname>MessageGroup</classname>s is by
configuring <classname>MessageGroupStoreReaper</classname>. However since <classname>MessageGroup</classname>s are expired by calling
<code>MessageGroupStore.expireMessageGroup(groupId)</code>, <classname>MessageGroupStoreReaper</classname> is not the only option and can be
accomplished via <classname>ControlBus</classname> or by simply invoking a method on <classname>MessageGroupStore</classname> if you have reference to its instance.
Otherwise by itself this attribute has no behavior. It only serves as an indicator of what to do (drop or send to the output/reply channel) with Messages that are
still in the <classname>MessageGroup</classname> that is about to be expired.
Indicates that expired messages should be aggregated and sent to the 'output-channel' or 'replyChannel'
once their containing <classname>MessageGroup</classname> is expired (see <code>MessageGroupStore.expireMessageGroups(long)</code>).
One way of expiring <classname>MessageGroup</classname>s is by configuring a <classname>MessageGroupStoreReaper</classname>.
However <classname>MessageGroup</classname>s can alternatively be expired by simply calling
<code>MessageGroupStore.expireMessageGroup(groupId)</code>. That could be accomplished via a Control Bus operation
or by simply invoking that method if you have a reference to the <classname>MessageGroupStore</classname> instance.
Otherwise by itself this attribute has no behavior. It only serves as an indicator of what to do (discard or send to the output/reply
channel) with Messages that are still in the <classname>MessageGroup</classname> that is about to be expired.
<emphasis>Optional</emphasis>.</para>
<para><emphasis>Default - 'false'</emphasis>.</para>
</callout>

10
spring-integration-core/src/main/resources/org/springframework/integration/config/xml/spring-integration-2.0.xsd
View File

@@ -2511,11 +2511,11 @@ Name of the header whose value will be used to route messages
<xsd:attribute name="send-partial-result-on-expiry" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Tells that partially aggregated messages should be sent to the 'output-channel' or 'replyChannel'
once the particular MessageGroup had expired. One of the ways of expiring MessageGroups is by
configuring MessageGroupStoreReaper. However since MessageGroups are expired by calling
MessageGroupStore.expireMessageGroup(groupId), MessageGroupStoreReaper is not the only option and can be
accomplished via ControlBus or by simply invoking a method on MessageGroupStore if you have reference to its instance.
Specifies whether messages that expired should be aggregated and sent to the 'output-channel' or 'replyChannel'.
Messages are expired when their containing MessageGroup expires. One of the ways of expiring MessageGroups is by
configuring a MessageGroupStoreReaper. However MessageGroups can alternatively be expired by simply calling
MessageGroupStore.expireMessageGroup(groupId). That could be accomplished via a ControlBus operation
or by simply invoking that method if you have a reference to the MessageGroupStore instance.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>

10
spring-integration-core/src/main/resources/org/springframework/integration/config/xml/spring-integration-2.1.xsd
View File

@@ -2499,11 +2499,11 @@ Name of the header whose value will be used to route messages
<xsd:attribute name="send-partial-result-on-expiry" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Tells that partially aggregated messages should be sent to the 'output-channel' or 'replyChannel'
once the particular MessageGroup had expired. One of the ways of expiring MessageGroups is by
configuring MessageGroupStoreReaper. However since MessageGroups are expired by calling
MessageGroupStore.expireMessageGroup(groupId), MessageGroupStoreReaper is not the only option and can be
accomplished via ControlBus or by simply invoking a method on MessageGroupStore if you have reference to its instance.
Specifies whether messages that expired should be aggregated and sent to the 'output-channel' or 'replyChannel'.
Messages are expired when their containing MessageGroup expires. One of the ways of expiring MessageGroups is by
configuring a MessageGroupStoreReaper. However MessageGroups can alternatively be expired by simply calling
MessageGroupStore.expireMessageGroup(groupId). That could be accomplished via a ControlBus operation
or by simply invoking that method if you have a reference to the MessageGroupStore instance.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>