[cdi-dev] [JBoss JIRA] (CDI-710) Require default event ExecutorService to be managed on Java EE

[Martin Kouba (JIRA)]

    [ https://issues.jboss.org/browse/CDI-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448411#comment-13448411 ] 

Martin Kouba commented on CDI-710:
----------------------------------

bq. What about deprecating the default executor usage? Sounds like whatever implementations do it will always have a bad guess of the app expectations so it is an API to avoid anyway. It would also solve this ticket making it aligned in EE environments.

-10 
* we don't have any "exact numbers" about expectations and usage
* CDI 2 is also targeted to other environments, not only Java EE

> Require default event ExecutorService to be managed on Java EE
> --------------------------------------------------------------
>
>                 Key: CDI-710
>                 URL: https://issues.jboss.org/browse/CDI-710
>             Project: CDI Specification Issues
>          Issue Type: Feature Request
>          Components: Events
>            Reporter: Guillermo González de Agüero
>
> When running on a Java EE environment, CDI should use a managed executor service by default for asynchronous operations.
> This is already required by the JAX-RS 2.1 spec (http://download.oracle.com/otndocs/jcp/jaxrs-2_1-pfd-spec/index.html), section 5.8:
> {quote}In an environment that supports the Concurrency Utilities for Java EE [13], such as the Java EE Full Profile, implementations MUST use ManagedExecutorService and ManagedScheduledExecutorService, respectively. The reader is referred to the Javadoc of ClientBuilder for more information about executor services.{quote}
> Containers will presumably offer monitoring features and thread pool configuration options for managed executor services.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)