camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: component lifecycle and cache
Date Tue, 24 Jan 2012 15:23:21 GMT
On Tue, Jan 24, 2012 at 4:18 PM, Babel <chpache@gmail.com> wrote:
> Thanks for your answer
>
> For more detail, I did not found how Camel manage its components. Are those
> two assertion true?
>  - a component is started when added to the camel context

Yes, well its when you use the component for the first time its started.

If you use the addComponent API from CamelContext, then the component
is not started.
If you use getComponent, then the component is started.


>  - a component is destroy only when the camel context is stopped (and not
> for example when there is no more endpoint corresponding to that component)
>

Yes.

> Thanks for your advices and sorry if you already answered that question, but
> I didn't find it.
>
> Babel
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/component-lifecycle-and-cache-tp4946235p5281954.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
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/

Mime
View raw message