camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CAMEL-1151) Abstraction of ExecutorService for working in managed environments (J2EE servers)
Date Sat, 06 Mar 2010 08:27:45 GMT

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

Claus Ibsen resolved CAMEL-1151.
--------------------------------

    Resolution: Duplicate

Duplicate of CAMEL-1437.

There is a SPI now which you can use to hook into J2EE by implementing the SPI and use the
WorkManager API to create/lookup the thread pools of choice.

> 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
>            Assignee: Claus Ibsen
>             Fix For: 2.3.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.


Mime
View raw message