A custom ThreadPoolFactory could be sufficient: As I have a similar task (although I decided to stick with Camel-managed tasks for the time being), I prototyped an ExecutorService-to-WorkManager bridge, i.e. an ExecutorService that delegates Runnables/Callables as commonj Work objects to a WorkManager instance, and the returning the resulting WorkItem back as a Future. A custom ThreadPoolFactory would return these ExecutorService instances instead ones provided by DefaultTHreadPoolFactory.
I must admit this is far from being stable (especially the corresponding ScheduledExecutorService/Timer bridge), but it would also be applicable to other frameworks that rely on ExecutorService. If there's interest in this, I can pursue this a bit further. cheers Christian -- View this message in context: http://camel.465427.n5.nabble.com/Thread-pool-for-Camelcontext-tp470625p5713358.html Sent from the Camel - Users mailing list archive at Nabble.com.
