You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2012/06/18 10:43:43 UTC
[jira] [Created] (CAMEL-5375) Add
CompletionAwareAggregationStrategy to the aggregator EIP
Claus Ibsen created CAMEL-5375:
----------------------------------
Summary: Add CompletionAwareAggregationStrategy to the aggregator EIP
Key: CAMEL-5375
URL: https://issues.apache.org/jira/browse/CAMEL-5375
Project: Camel
Issue Type: New Feature
Components: camel-core
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 2.10.0
When people use the aggregator EIP, then they use the aggregation strategy interface.
What is needing sometimes is a callback when the aggregated exchange is done, so you can do any custom cleanup/logic there, before the exchange is being routed out of the aggregator.
Without this you would need to do this logic afterwards in the route, by calling a bean/processor. This is not so nice. So having a onComplete callback method in your aggregation strategy is better.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-5375) Add
CompletionAwareAggregationStrategy to the aggregator EIP
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-5375.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.9.3
Backported to 2.9 branch as well, as its fully backwards compatible
> Add CompletionAwareAggregationStrategy to the aggregator EIP
> ------------------------------------------------------------
>
> Key: CAMEL-5375
> URL: https://issues.apache.org/jira/browse/CAMEL-5375
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.9.3, 2.10.0
>
>
> When people use the aggregator EIP, then they use the aggregation strategy interface.
> What is needing sometimes is a callback when the aggregated exchange is done, so you can do any custom cleanup/logic there, before the exchange is being routed out of the aggregator.
> Without this you would need to do this logic afterwards in the route, by calling a bean/processor. This is not so nice. So having a onComplete callback method in your aggregation strategy is better.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira