You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2010/03/06 09:25:44 UTC
[jira] Issue Comment Edited: (CAMEL-1437) Executor Service - We
need SPI for ExecutorServiceResolver
[ https://issues.apache.org/activemq/browse/CAMEL-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58068#action_58068 ]
Claus Ibsen edited comment on CAMEL-1437 at 3/6/10 8:25 AM:
------------------------------------------------------------
trunk: 919711, 919713.
Introduced {{org.apache.camel.spi.ExecutorServiceStrategy}} which you should access from {{CamelContext}} to create thread pools.
was (Author: davsclaus):
trunk: 919711.
Introduced {{org.apache.camel.spi.ExecutorServiceStrategy}} which you should access from {{CamelContext}} to create thread pools.
> Executor Service - We need SPI for ExecutorServiceResolver
> ----------------------------------------------------------
>
> Key: CAMEL-1437
> URL: https://issues.apache.org/activemq/browse/CAMEL-1437
> Project: Apache Camel
> Issue Type: New Feature
> Affects Versions: 2.0.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.3.0
>
>
> A SPI so for ExecutorService so they can setup an hook in their impl of choice, eg WebSphere WorkManager. Or some of the build in the JDK.
> This applies to:
> - components (DefaultComponent)
> - various processors
> Currently this can be done for the component as there is a setExecutorService, but it should be easier to set a global configuration
> For the processor this has to be done individually in the route DSL. It should also support fetching for the global configuration.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.