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 2009/05/23 18:56:50 UTC
[jira] Updated: (CAMEL-1151) Abstraction of ExecutorService for
working in managed environments (J2EE servers)
[ https://issues.apache.org/activemq/browse/CAMEL-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-1151:
-------------------------------
Fix Version/s: (was: Future)
2.1.0
Issue Type: New Feature (was: Bug)
> Abstraction of ExecutorService for working in managed environments (J2EE servers)
> ---------------------------------------------------------------------------------
>
> Key: CAMEL-1151
> URL: https://issues.apache.org/activemq/browse/CAMEL-1151
> Project: Apache Camel
> Issue Type: New Feature
> Reporter: Claus Ibsen
> Fix For: 2.1.0
>
>
> See CAMEL-1098
> quote start
> The unfortunate issue here is that there is another API (Timer) that
> provides the equivalent to ScheduledExecutorService. This API is
> significantly different to the Java SE concurrent equivalents that
> would make the previous approach of proxying the interfaces very
> difficult. So for now, it looks like there is no clean way to use
> ScheduledExecutorService implementations in a managed environment.
> Moving forward, my suggestion would be for Camel to have it's own
> abstraction, similar to Spring's TaskExecutor, that would allow for
> the configuration of thread management whether running in a managed
> container or not.
> JSR 236 offers hope for the future.
> Tim...
> quote end
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.