[
https://issues.apache.org/jira/browse/CAMEL-4298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13078670#comment-13078670
]
Christian Schneider commented on CAMEL-4298:
--------------------------------------------
This was intentional as I think the change is not very difficult to follow and
mainly hits component developers. I think we should remove the Strategy now or
in the next minor release.
> 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
