I think that is not necessary. I only wanted to check if it is normal
behaviour or if we have a bug.
Strangely it seemed to not hang in earlier versions. Not sure why though.
Christian
Am 18.09.2012 15:39, schrieb Claus Ibsen:
As the templates (their default impls) is associated with a
CamelContext, we could eventually also add logic, to enlist the
template in a list of active template stored on the camel context. So
when camel context shutdown, it could shutdown the templates as well -
as a fail safe.
And if a client is calling stop on a template manually, we would then
need to unregistered it from the list on camel context. To avoid the
list to grow large if people create a lot of templates and stop them
again.
So it would be doable to build-in this "failsafe" for the end users.
But ideally its best if users call stop when they no longer need the
template. For example if its just a one-stop usage.
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
