March 2012 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-210) BeanManager.createBean() should use type variables instead of wildcards

by Jozef Hartinger (JIRA)

Jozef Hartinger created CDI-210: ----------------------------------- Summary: BeanManager.createBean() should use type variables instead of wildcards Key: CDI-210 URL: https://issues.jboss.org/browse/CDI-210 Project: CDI Specification Issues Issue Type: Feature Request Components: Portable Extensions Affects Versions: 1.1.EDR1 Reporter: Jozef Hartinger Fix For: 1.1 (Proposed) {code} public Bean<?> createBean(BeanAttributes<?> attributes, Class<?> beanClass, InjectionTarget<?> injectionTarget) public Bean<?> createBean(BeanAttributes<?> attributes, Class<?> beanClass, Producer<?> producer) {code} I propose: {code} public <T> Bean<T> createBean(BeanAttributes<T> attributes, Class<T> beanClass, InjectionTarget<T> injectionTarget) public <T> Bean<T> createBean(BeanAttributes<T> attributes, Class<?> beanClass, Producer<T> producer); {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (CDI-112) Clarify how alternatives are enabled

by Shane Bryzak (JIRA)

Clarify how alternatives are enabled ------------------------------------ Key: CDI-112 URL: https://issues.jboss.org/browse/CDI-112 Project: CDI Specification Issues Issue Type: Clarification Components: Beans Affects Versions: 1.0 Reporter: Shane Bryzak The spec is open to interpretation about how alternatives are enabled. One popular interpretation is that alternatives must be enabled within the same bean archive that contains the alternative bean. However, it might be worth considering the merit of enabling an alternative from a deployment archive that contains the bean archive. For example, suppose we have the following deployment archive: foo.war /WEB-INF beans.xml /lib bar.jar /META-INF beans.xml /com /acme AlternativeBean.class It may be worth allowing AlternativeBean.class (a class annotated with @Alternative) to be enabled by listing it in the <alternatives> section of foo.war/WEB-INF/beans.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

4
8
0 / 0

[JBoss JIRA] (CDI-188) Bean in different wars should be allowed to have the same EL name

by Stuart Douglas (Created) (JIRA)

Bean in different wars should be allowed to have the same EL name ----------------------------------------------------------------- Key: CDI-188 URL: https://issues.jboss.org/browse/CDI-188 Project: CDI Specification Issues Issue Type: Bug Reporter: Stuart Douglas Normally two beans with the same @Named would be treated as an error. If they are in sperate war's this should be allowed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

6
11
0 / 0

[JBoss JIRA] (CDI-202) Clarify when BeanManager.createBeanAttributes(AnnotatedMember) returns an alternative

by Jozef Hartinger (Created) (JIRA)

Clarify when BeanManager.createBeanAttributes(AnnotatedMember) returns an alternative ------------------------------------------------------------------------------------- Key: CDI-202 URL: https://issues.jboss.org/browse/CDI-202 Project: CDI Specification Issues Issue Type: Clarification Components: Beans Affects Versions: 1.1.EDR1 Reporter: Jozef Hartinger Fix For: 1.1 (Proposed) Currently, a producer field/method is an alternative if it is annotated with @Alternative or an alternative stereotype or the class declaring the field/method is annotated this way. However, when the BeanManager.createBeanAttributes(AnnotatedMember) method is called, the container has no access to the bean that declares the member. Therefore, the specification should clarify whether the container * should examine the AnnotatedType for @Alternative or alternative stereotypes * should try to infer the declaring bean (probably not possible since multiple beans may exist, each of them possibly modified in the ProcessBeanAttributes phase, etc.) * should make an assumption (e.g. the bean that declares the returned BeanAttributes is always assumed not to be an alternative) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (CDI-149) AnnotationLiteral in the CDI API does not cache the hashCode

by Stuart Douglas (JIRA)

AnnotationLiteral in the CDI API does not cache the hashCode ------------------------------------------------------------ Key: CDI-149 URL: https://issues.jboss.org/browse/CDI-149 Project: CDI Specification Issues Issue Type: Bug Reporter: Stuart Douglas Instead it is calculated each time using reflection, which could result in performance problems if lots of annotation literals are in use -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

4
6
0 / 0

[JBoss JIRA] (CDI-208) ConversationScoped.class should be the value of the conversation lifecycle event qualifier

by Jozef Hartinger (Created) (JIRA)

ConversationScoped.class should be the value of the conversation lifecycle event qualifier ------------------------------------------------------------------------------------------ Key: CDI-208 URL: https://issues.jboss.org/browse/CDI-208 Project: CDI Specification Issues Issue Type: Clarification Components: Contexts Affects Versions: 1.1.EDR1 Reporter: Jozef Hartinger Priority: Minor Fix For: 1.1 (Proposed) {quote}An event with the ServletRequestEvent as the payload and with qualifier @Initialized(ConversationContext.class) is fired when the conversation context is initialized and an event with qualifier @Destroyed(ConversationContext.class) when the conversation context is destroyed.{quote} ConversationScoped.class should be used instead of ConversationContext.class -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
4
0 / 0

[JBoss JIRA] (CDI-212) Clarify BeanManager.createBean()

by Jozef Hartinger (JIRA)

Jozef Hartinger created CDI-212: ----------------------------------- Summary: Clarify BeanManager.createBean() Key: CDI-212 URL: https://issues.jboss.org/browse/CDI-212 Project: CDI Specification Issues Issue Type: Clarification Components: Portable Extensions Affects Versions: 1.1.EDR1 Reporter: Jozef Hartinger Fix For: 1.1 (Proposed) It is unclear from the specification whether the BeanManager.createBean() method should ever return an implementation of the Decorator or Interceptor interface. Method parameters of the createBean() method provide all the necessary information for constructing a Decorator implementation. Therefore, IMHO the method should return a container-provided Decorator implementation if the set of stereotypes returned by BeanAttributes.getStereotypes contains javax.decorator.Decorator. On the other hand, Interceptors do not fit this model because the AnnotatedType of the bean class is not available to the method and using the reflection API to scan the bean class directly would not be consistent with the rest of the specification. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
4
0 / 0

[JBoss JIRA] (CDI-204) Clarify ProcessInjectionPoint type parameters

by Jozef Hartinger (Created) (JIRA)

Clarify ProcessInjectionPoint type parameters --------------------------------------------- Key: CDI-204 URL: https://issues.jboss.org/browse/CDI-204 Project: CDI Specification Issues Issue Type: Clarification Components: Portable Extensions Affects Versions: 1.1.EDR1 Reporter: Jozef Hartinger Priority: Minor Fix For: 1.1 (Proposed) {quote} The container must fire an event for every injection point of every Java EE component class supporting injection that may be instantiated by the container at runtime. The event object must be of type javax.enterprise.inject.spi.ProcessInjectionPoint<T,X> where T is the bean class of the bean that declares the injection point, and X is the declared type of the injection point. {quote} The first paragraph implies that this event may be fired for injection points not necesarilly defined on a bean. In that case, the value of the T type parameter is unclear. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (CDI-152) Access the the web.xml from CDI extensions

by Brian Leathem (JIRA)

Access the the web.xml from CDI extensions ------------------------------------------ Key: CDI-152 URL: https://issues.jboss.org/browse/CDI-152 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Brian Leathem Currently it is not possible to access the web.xml file from CDI extensions in a portable way, since the ServletContext is not available from CDI extensions (at least in EE enviroments). I filed a Servlet spec issue to make the web.xml file accessible, prior to the the ServletContext being initialized: http://java.net/jira/browse/SERVLET_SPEC-9 Perhaps as an alternative solution, CDI could do something to delay CDI extensions from loading until the ServletContext is available? Since this is the case for Servlet environments, would it not be acceptable for EE environments as well? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
3
0 / 0

[JBoss JIRA] (CDI-182) Cluster Lifecycle Events

by Kristoffer Sjögren (Created) (JIRA)

Cluster Lifecycle Events ------------------------ Key: CDI-182 URL: https://issues.jboss.org/browse/CDI-182 Project: CDI Specification Issues Issue Type: Feature Request Components: Events Affects Versions: 1.1 (Proposed) Environment: Any java environment. Reporter: Kristoffer Sjögren Priority: Minor Fix For: 1.1 (Proposed) CDI 1.1 defines a set of lifecycle events related to different context within the application. We see a need to also define cluster lifecycle events for applications. These events could, for example, be used for subscribing/allocating and unsubscribing/deallocating external services/resources. More specifically, a @Cluster event that gets fired when an application gets @Initialized in the cluster, that is, post @Application @Initialized. And another @Cluster event that gets fired when the application get @Destroyed in the cluster, that is, pre @Application @Destroyed. These events only fires once per application and cluster, independent on how many cluster instances exists. Events are fault tolerant meaning that events are not affected by failing instances going out-of-service, as long as the cluster is still working. Notice that the @Destroyed event is of course only invoked if the cluster terminates gracefully. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev March 2012