Just a proposal : it might be great to write in the documentation a post
about how to manage the ".end()" instruction : what components need it? how
two not "cross" them and avoid confusions?
Like in :
.loop(3)
.to(...)
.split(...)
.end() --> what END is it?
-
http://developpef.blogspot.c
OK, after a test, you're right, it is now working as expected.
Thanks for pointing me this tip!
-
http://developpef.blogspot.com
--
View this message in context:
http://camel.465427.n5.nabble.com/Split-an-empty-list-tp5728214p5728225.html
Sent from the Camel - Users mailing list archive at
Hi
Yes its this eip
http://camel.apache.org/composed-message-processor.html
The Camel splitter has a built-in aggregation stragegy which is much
easier to use than split + aggregate.
See the example on the page above, about using ONLY splitter.
On Wed, Feb 27, 2013 at 1:28 PM, developpef wrote
Well, after my SPLIT I use an aggregation Strategy with completionPredicate
to Exchange.SPLIT_COMPLETE.
So if I understand, I would rather write :
.split(body(), myAggregationStrategy)
(... split operations ...)
.end()
rather than :
.split(body())
(... split operations ...)
.aggregate(...)
.com
On Wed, Feb 27, 2013 at 11:46 AM, developpef wrote:
> Hello,
>
> Here is what happens :
>
> My route is :
>
> from("direct:inside")
> .log(LoggingLevel.INFO, " start")
> .beanRef(MY_SERVICE, "retrieveDataList")
> .log(LoggingLevel.INFO, " before split ${body}")
> .split(body())
> .log(Logg
