Loading Camel processors in separate classloaders

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Loading Camel processors in separate classloaders

elihusmails
I am building a system that relies on Apache Camel for data routing.  Within
these routes will be custom processors and 3rd party processors (plug-ins).
I would like the processors to run inside their own classloaders for
protection and to protect the core system.  Is this something that Karaf can
support since I don't think its possible for Camel to support this
functionality.

Thanks,
Mark
Reply | Threaded
Open this post in threaded view
|

Re: Loading Camel processors in separate classloaders

luke
Can't you simply use a Processor which uses list of Processor instances looked up from OSGi service registry and call them using an interface? Then you'll have separate class loaders for every service instance.

Best regards,
Lukasz

> I am building a system that relies on Apache Camel for data routing.  Within
> these routes will be custom processors and 3rd party processors (plug-ins).
> I would like the processors to run inside their own classloaders for
> protection and to protect the core system.  Is this something that Karaf can
> support since I don't think its possible for Camel to support this
> functionality.
>
> Thanks,
> Mark