Also note that the same scheme exists for spring OOTB where the TaskExecutor is the abstraction on top of all of these.
2011/5/6 Claus Ibsen <[email protected]> > On Fri, May 6, 2011 at 4:54 PM, Tarun Ramakrishna <[email protected]> > wrote: > > Actually this could have been simply solved if camel core and all > > camel components delegated their threading needs to a > > java.util.concurrent.ThreadFactory. Then one could have centralized > > thread management. Unfortunately even if Camel is well behaved many of > > its components are not and even associated units like ActiveMQ don't > > seem to allow you to customize thread creation. But maybe there is a > > way to do this that I am not aware of. > > > > Came sure does that. There is a SPI for that > > http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/spi/ExecutorServiceStrategy.html > > It allows to plugin 3rd party providers. So we can provide a CommonJ > bridge for that out of the box. > > But yes for 3rd party components they need to leverage that SPI as > well. Some of the components do that already. > But there may be some that uses their own abstraction. For example Jetty > etc. > > > > > -- > 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/ > -- -- David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen
