[
https://issues.apache.org/jira/browse/CAMEL-4298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083174#comment-13083174
]
Claus Ibsen commented on CAMEL-4298:
------------------------------------
CAMEL-4244 introduced a few other issues so I am going to bridge back parts of
the old API. As well to have better API documentation as the current dont have,
so end user would not understand whats the difference between among others the
following methods etc.
{code}
ExecutorService getDefaultExecutorService(String ref, Object source);
ExecutorService getExecutorService(ThreadPoolProfile profile, Object
source);
ExecutorService createExecutorService(ThreadPoolProfile profile, Object
source);
{code}
> 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: Claus Ibsen
> 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
