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 2011/08/12 19:10:27 UTC

[jira] [Resolved] (CAMEL-4298) Add back ExecutorServiceStrategy and mark it as @deprecated

     [ https://issues.apache.org/jira/browse/CAMEL-4298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-4298.
--------------------------------

    Resolution: Fixed

Added back the ExecutorServiceStrategy interface, and a delegate implementation that uses the new ExecutorServiceManager. Added the old unit test to ensure the strategy still works as expected.

Updated the wiki documentation as well.

> 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