The Camel In Action book says: "When you need to use a different thread
pool provider (for example, a provider from a Java EE server), you can
create a custom ExecutorServiceManager to work with the provider. "


On IBM Liberty, by turning on the feature "concurrent/1.0" one can get an
ExecutorService. I would like to use this ExecutorService.

My understanding is that I can create a ThreadPoolFacotory that wraps this
ExecutorService.

As long as that ThreadPoolFactory is a Spring bean, Camel will find it and
use it as the default.

Is that correct? It does not appear to use the ExecutorService from
Liberty. Does does it have to be set explicitly on the Camel context?

Reply via email to