Add a transformation from CSV to Map object before the aggregator. Then let the aggregator store a list of maps, or a map of maps, in the exchange body.
You can then use this list in any subsequent transformation. It all depends on what it is you intend to do with the data after it has been aggregated. // Pontus On Wed, Mar 20, 2013 at 10:48 AM, Jothi <codeintheo...@gmail.com> wrote: > Thanks for the reply. > > Would I be able to do the following? The 3 CSV files will contain different > information. I need to poll for these 3 files and get 3 Map objects out of > those 3 CSV files. I've seen the aggregation examples from the Camel > documentation, but there we combine the old and the new exchange. If I had > to do that, I will end up with one Map object which is not what I want. If I > use the headers to store the Map, am I exploiting the very purpose of Camel > headers? Is there a better way to do this? > > Regards, > Joe > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-Aggregator-Strategy-Question-tp5729337p5729489.html > Sent from the Camel - Users mailing list archive at Nabble.com.
