Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: neutral (nike.apache.org: 216.139.236.26 is neither permitted
 nor denied by domain of chpache@gmail.com)
Date: Tue, 24 Jan 2012 07:18:33 -0800 (PST)
From: Babel <chpache@gmail.com>
To: users@camel.apache.org
Message-ID: <1327418313849-5281954.post@n5.nabble.com>
In-Reply-To: 
 <CAGB5yN=c7wjE+n3_8Upzqpso3NmcUMo8Z6CbrRTKOG_imBfu4Q@mail.gmail.com>
References: <1319814246558-4946235.post@n5.nabble.com>
 <CAGB5yN=c7wjE+n3_8Upzqpso3NmcUMo8Z6CbrRTKOG_imBfu4Q@mail.gmail.com>
Subject: Re: component lifecycle and cache
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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
 - 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)

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.