-
May 10th, 2010, 09:49 AM
#1
2.0.0M4 Aggregator timeout attribute, where did it go?
Hello and thanks for the work on a product which appears to have great potential and save me lots of work!
I've noticed a number of changes in my migration from M3 to M4 related the release strategies and the "timeout" attribute for the aggregator tag. I've search a bit and have been unsuccessful in determining how I'm supposed to set the timeout value.
Do I need to create my own "Message Store", then reference the store inside the aggregator? Does the new MessageGroupStoreReaper play some part in the newly missing "timeout" attribute?
<code>
<!-- M3 version -->
<aggregator input-channel="appChannel"
output-channel="collectedChannel"
correlation-strategy="partyCorrelationStrategy"
completion-strategy="falseCompletionStrategy"
send-partial-result-on-timeout="true"
timeout="60000">
</aggregator>
</code>
<code>
<!-- M4 version -->
<aggregator input-channel="appChannel" output-channel="collectedChannel" discard-channel="logger"
correlation-strategy="partyCorrelationStrategy"
release-strategy="falseReleaseStrategy"
send-partial-result-on-expiry="true">
</aggregator>
</code>
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules