Are there any tricks or patterns to use when it comes to needing to manage the lifecyle of components used in Camel routes. For instance if I write a custom Processor that creates something like a PreparedStatement how can I make sure its is close()'d when the CamelContext shuts down.

Thanks
Tim

Reply via email to