cdi-dev August 2017

cdi-dev@lists.jboss.org

3 participants
34 discussions

[JBoss JIRA] (CDI-711) BeanConfigurator cannot be used to define alternative beans enabled for an application

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-711?page=com.atlassian.jira.plugin.sy... ] Martin Kouba updated CDI-711: ----------------------------- Fix Version/s: 2.1 (Discussion) > BeanConfigurator cannot be used to define alternative beans enabled for an application > --------------------------------------------------------------------------------------- > > Key: CDI-711 > URL: https://issues.jboss.org/browse/CDI-711 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Portable Extensions > Affects Versions: 2.0 .Final > Reporter: Martin Kouba > Fix For: 2.1 (Discussion) > > > Custom bean implementations may implement {{Prioritized}} interface. There should be probably a {{BeanConfigurator.priority(int priority)}} method. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (CDI-711) BeanConfigurator cannot be used to define alternative beans enabled for an application

by Martin Kouba (JIRA)

Martin Kouba created CDI-711: -------------------------------- Summary: BeanConfigurator cannot be used to define alternative beans enabled for an application Key: CDI-711 URL: https://issues.jboss.org/browse/CDI-711 Project: CDI Specification Issues Issue Type: Feature Request Components: Portable Extensions Affects Versions: 2.0 .Final Reporter: Martin Kouba Custom bean implementations may implement {{Prioritized}} interface. There should be probably a {{BeanConfigurator.priority(int priority)}} method. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

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

by Guillermo González de Agüero (JIRA)

[ https://issues.jboss.org/browse/CDI-710?page=com.atlassian.jira.plugin.sy... ] Guillermo González de Agüero updated CDI-710: --------------------------------------------- Description: 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. was: When runnin 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. > 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)

7 years, 4 months

1
0
0 / 0

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

by Guillermo González de Agüero (JIRA)

Guillermo González de Agüero created CDI-710: ------------------------------------------------ Summary: 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 runnin 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)

7 years, 4 months

1
0
0 / 0

← Newer
1
2
3
4
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev August 2017