[
https://issues.apache.org/jira/browse/CAMEL-4298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082534#comment-13082534
]
Claus Ibsen commented on CAMEL-4298:
------------------------------------
There is now a problem in camel-jms as it used the ExecutorServiceStrategy to
create a cached thread pool. This is no longer possible. I added a TODO in the
camel-jms module.
But we may want to consider these API changes again. IMHO its better to have
the API resemble what people already know from the JDK API. Alternative we may
have some builder method on thread pool profile, so you can ask it to create a
cached thread pool.
> Add back ExecutorServiceStrategy and mark it as @deprecated
> -----------------------------------------------------------
>
> Key: CAMEL-4298
> URL: https://issues.apache.org/jira/browse/CAMEL-4298
> Project: Camel
> Issue Type: Task
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Christian Schneider
> Fix For: 2.9.0
>
>
> The old ExecutorServiceStrategy was refacted into ExecutorServiceManager. But
> it was removed. This was a mistake as it breaks backwards compatibility, and
> people are not given a reasonable time to adjust.
> So we should add back the ExecutorServiceStrategy and have it marked as
> @deprecated. It can then just under the hood, use the ExecutorServiceManager.
> Then in a future Camel release we can removed the @deprecated
> ExecutorServiceStrategy (for example Camel 3.0, or in eg 1 year from now)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
