camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CAMEL-1722) AggregationStrategy in Splitter, Aggregagator, Multicast - IN or OUT
Date Mon, 22 Jun 2009 10:10:35 GMT

     [ 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.


Mime
View raw message