You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by mathieuJ <ma...@gmail.com> on 2012/04/20 11:01:19 UTC

completionSize

Hi,

I have done a migration of Camel and i use completionTimeOut for my
aggregates.

But i would prefer used CompletionSize, with a dynamic size which is
register with a split before.

from(TARIF_LISTE_SIMULATION).routeId(TARIF_LISTE_SIMULATION)

	.bean(HeaderSetter.class, HeaderSetter.SET_ODEON_EXCHANGE_ID_HEADER)

       
.split(ExpressionBuilder.beanExpression(TarificationSimulationSpliter.class,
		                TarificationSimulationSpliter.SPLIT))
	
	.parallelProcessing()

	.bean(TarificationBean.class, TarificationBean.METHOD_NAME)
		        
       
.aggregate(DefaultAggregationStrategy.getInstance()).header(UsefulConstants.ODEONEXCHANGEID)
		        
        .bean(VoidProcessor.class).completionTimeout(30000)

        .end();

but i don't see how to use this and i looking for example.

regard's

Mathieu

--
View this message in context: http://camel.465427.n5.nabble.com/completionSize-tp5653718p5653718.html
Sent from the Camel Development mailing list archive at Nabble.com.

Re: completionSize

Posted by Claus Ibsen <cl...@gmail.com>.
Hi

First of all please use the @user mailing list for your Camel questions/help.
As we say here
http://camel.apache.org/support


The aggregate EIP do support dynamic values, see the documentation
http://camel.apache.org/aggregator2



Btw the splitter EIP has built-in support for aggregation out of the box.
So its like the composed message processor EIP
http://camel.apache.org/composed-message-processor.html

However the webpage has not been updated to mention that.
If you got Camel in Action book check chapter 8.

If that's the use-case you are implementing, then thats maybe easier.
Than using both splitter + aggregator.



On Fri, Apr 20, 2012 at 11:01 AM, mathieuJ <ma...@gmail.com> wrote:
> Hi,
>
> I have done a migration of Camel and i use completionTimeOut for my
> aggregates.
>
> But i would prefer used CompletionSize, with a dynamic size which is
> register with a split before.
>
> from(TARIF_LISTE_SIMULATION).routeId(TARIF_LISTE_SIMULATION)
>
>        .bean(HeaderSetter.class, HeaderSetter.SET_ODEON_EXCHANGE_ID_HEADER)
>
>
> .split(ExpressionBuilder.beanExpression(TarificationSimulationSpliter.class,
>                                TarificationSimulationSpliter.SPLIT))
>
>        .parallelProcessing()
>
>        .bean(TarificationBean.class, TarificationBean.METHOD_NAME)
>
>
> .aggregate(DefaultAggregationStrategy.getInstance()).header(UsefulConstants.ODEONEXCHANGEID)
>
>        .bean(VoidProcessor.class).completionTimeout(30000)
>
>        .end();
>
> but i don't see how to use this and i looking for example.
>
> regard's
>
> Mathieu
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/completionSize-tp5653718p5653718.html
> Sent from the Camel Development mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/