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/16 18:28:35 UTC
[jira] Created: (CAMEL-1722) AggregationStrategy in Splitter,
Aggregagator, Multicast - IN or OUT
AggregationStrategy in Splitter, Aggregagator, Multicast - IN or OUT
--------------------------------------------------------------------
Key: CAMEL-1722
URL: https://issues.apache.org/activemq/browse/CAMEL-1722
Project: Apache Camel
Issue Type: Improvement
Components: camel-core
Affects Versions: 2.0-M2
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 2.0.0
Force the wrapping of a pipeline so its always IN that end users should use to get the payload.
Now it depends on the number of sub processors in the route. If you only have 1 processor then there is no pipeline wrapped.
If you have 2+ then Camel will wrap a pipeline.
We should *always* force a pipeline then its consistent to use IN
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-1722) AggregationStrategy in Splitter,
Aggregagator, Multicast - IN or OUT
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52389#action_52389 ]
Claus Ibsen commented on CAMEL-1722:
------------------------------------
See nabble
http://www.nabble.com/Information-required-about-IN-OUT-pattern-of-splitter-EIP-td24053037.html
> AggregationStrategy in Splitter, Aggregagator, Multicast - IN or OUT
> --------------------------------------------------------------------
>
> Key: CAMEL-1722
> URL: https://issues.apache.org/activemq/browse/CAMEL-1722
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.0-M2
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.0.0
>
>
> Force the wrapping of a pipeline so its always IN that end users should use to get the payload.
> Now it depends on the number of sub processors in the route. If you only have 1 processor then there is no pipeline wrapped.
> If you have 2+ then Camel will wrap a pipeline.
> We should *always* force a pipeline then its consistent to use IN
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CAMEL-1722) AggregationStrategy in Splitter,
Aggregagator, Multicast - IN or OUT
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-1722.
--------------------------------
Resolution: Fixed
trunk: 787184.
Now when using {{AggregationStrategy}} the body is always in IN and the OUT is null. This eliminates the confusion of whether to use IN or OUT.
> AggregationStrategy in Splitter, Aggregagator, Multicast - IN or OUT
> --------------------------------------------------------------------
>
> Key: CAMEL-1722
> URL: https://issues.apache.org/activemq/browse/CAMEL-1722
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.0-M2
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.0.0
>
>
> Force the wrapping of a pipeline so its always IN that end users should use to get the payload.
> Now it depends on the number of sub processors in the route. If you only have 1 processor then there is no pipeline wrapped.
> If you have 2+ then Camel will wrap a pipeline.
> We should *always* force a pipeline then its consistent to use IN
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.