Hi Guillaume,
indeed, it looks cleaner. Let me take a deeper look on the code but it
sounds good.
Regards
JB
On 07/28/2011 10:14 AM, Guillaume Nodet wrote:
I found another way which I think is cleaner. I've added a single
Container interface with a singleton which is called back whenever a
CamelContext is created. The implementation can then add a
LifecycleListener or register any other SPI object.
See
https://github.com/gnodet/camel/commit/a13b4fc19b7fd9a1f6b7e945353d1246151267af
Feedback welcome!
On Thu, Jul 21, 2011 at 11:22, Guillaume Nodet<gno...@gmail.com> wrote:
For ServiceMix, we are in need for having *global* interceptors, i.e.
some kind of static list of interceptors and other strategies. The
main use case is that users would deploy plain camel routes and
ServiceMix would kick in and configure its interceptors but without
any need for the user to change its route.
I'm not sure exactly all the SPI we'd need yet, but things like
InterceptStrategy, ProcessorFactory or EndpointStrategy may be needed.
So this email is just a heads up and to start any discussion ...
--
------------------------
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
