Thanks,Claus:
The real problem is spring doesn't understand the camel's xml schema. For
example:
<from uri="bean:beanId....">
the camel processor may dependency on a spring bean by the beanId; but the
spring know nothing about this;
So I am wondering if camel has carefully deal the destroy life cycle? I try
to check the source code of camel, but still know nothing about this;
============================================================================
On Fri, Apr 1, 2011 at 9:20 AM, ext2 <[email protected]> wrote:
>
>
> Hi:
> With spring, caml processors may depend on many beans. Could camel
> will ensure the camelcontext will be destroy before all the dependencies
> while spring context is destroy?
>
>
Check the spring documentation how it allows you to configure ordering
between beans. Thats normally the depends-on attribute you can use.
>
>
--
Claus Ibsen
-----------------
FuseSource
Email: [email protected]
Web: http://fusesource.com
CamelOne 2011: http://fusesource.com/camelone2011/
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
