You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2009/06/10 11:29:35 UTC
[jira] Created: (CAMEL-1691) Filter EIP should mark an exchange as
filtered so aggregator know this
Filter EIP should mark an exchange as filtered so aggregator know this
----------------------------------------------------------------------
Key: CAMEL-1691
URL: https://issues.apache.org/activemq/browse/CAMEL-1691
Project: Apache Camel
Issue Type: Improvement
Components: camel-core
Affects Versions: 1.6.1
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 2.0.0
When you use split, aggregator or the likes that uses an aggregation strategy and you filter the message out then it still passed in into the aggregation strategy.
It should be skipped.
For instance below we want to split a message and filter out bad lines.
{code}
Predicate goodWord = body().contains("World");
from("direct:start")
.split(body(List.class), new MyAggregationStrategy())
.filter(goodWord)
.to("mock:filtered")
.end()
.to("mock:result");
{code}
See nabble:
http://www.nabble.com/Filtered-message-after-splitter-shows-up-after-aggregation-td23957958s22882.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (CAMEL-1691) Filter EIP should mark an
exchange as filtered so aggregator know this
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52198#action_52198 ]
Claus Ibsen edited comment on CAMEL-1691 at 6/11/09 12:56 AM:
--------------------------------------------------------------
trunk: 783663,783675
New header {{Exchange.FILTERED}} as a Boolean to indicate if an Exchange is filtered.
Any filtered Exchanges will *not* be aggregated by the AggregatorStrategy.
was (Author: davsclaus):
trunk: 783663.
New header {{Exchange.FILTERED}} as a Boolean to indicate if an Exchange is filtered.
Any filtered Exchanges will *not* be aggregated by the AggregatorStrategy.
> Filter EIP should mark an exchange as filtered so aggregator know this
> ----------------------------------------------------------------------
>
> Key: CAMEL-1691
> URL: https://issues.apache.org/activemq/browse/CAMEL-1691
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 1.6.1
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.0.0
>
>
> When you use split, aggregator or the likes that uses an aggregation strategy and you filter the message out then it still passed in into the aggregation strategy.
> It should be skipped.
> For instance below we want to split a message and filter out bad lines.
> {code}
> Predicate goodWord = body().contains("World");
> from("direct:start")
> .split(body(List.class), new MyAggregationStrategy())
> .filter(goodWord)
> .to("mock:filtered")
> .end()
> .to("mock:result");
> {code}
> See nabble:
> http://www.nabble.com/Filtered-message-after-splitter-shows-up-after-aggregation-td23957958s22882.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1691) Filter EIP should mark an exchange
as filtered so aggregator know this
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52173#action_52173 ]
Claus Ibsen commented on CAMEL-1691:
------------------------------------
BTW: Looks like MulticastProcessor does not honor the end() I have to investigate the further
> Filter EIP should mark an exchange as filtered so aggregator know this
> ----------------------------------------------------------------------
>
> Key: CAMEL-1691
> URL: https://issues.apache.org/activemq/browse/CAMEL-1691
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 1.6.1
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.0.0
>
>
> When you use split, aggregator or the likes that uses an aggregation strategy and you filter the message out then it still passed in into the aggregation strategy.
> It should be skipped.
> For instance below we want to split a message and filter out bad lines.
> {code}
> Predicate goodWord = body().contains("World");
> from("direct:start")
> .split(body(List.class), new MyAggregationStrategy())
> .filter(goodWord)
> .to("mock:filtered")
> .end()
> .to("mock:result");
> {code}
> See nabble:
> http://www.nabble.com/Filtered-message-after-splitter-shows-up-after-aggregation-td23957958s22882.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-1691) Filter EIP should mark an exchange as
filtered so aggregator know this
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-1691.
--------------------------------
Resolution: Fixed
trunk: 783663.
New header {{Exchange.FILTERED}} as a Boolean to indicate if an Exchange is filtered.
Any filtered Exchanges will *not* be aggregated by the AggregatorStrategy.
> Filter EIP should mark an exchange as filtered so aggregator know this
> ----------------------------------------------------------------------
>
> Key: CAMEL-1691
> URL: https://issues.apache.org/activemq/browse/CAMEL-1691
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 1.6.1
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.0.0
>
>
> When you use split, aggregator or the likes that uses an aggregation strategy and you filter the message out then it still passed in into the aggregation strategy.
> It should be skipped.
> For instance below we want to split a message and filter out bad lines.
> {code}
> Predicate goodWord = body().contains("World");
> from("direct:start")
> .split(body(List.class), new MyAggregationStrategy())
> .filter(goodWord)
> .to("mock:filtered")
> .end()
> .to("mock:result");
> {code}
> See nabble:
> http://www.nabble.com/Filtered-message-after-splitter-shows-up-after-aggregation-td23957958s22882.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.