July 2012 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-172) Constructor injection of Java EE components

by Pete Muir (Created) (JIRA)

Constructor injection of Java EE components ------------------------------------------- Key: CDI-172 URL: https://issues.jboss.org/browse/CDI-172 Project: CDI Specification Issues Issue Type: Feature Request Affects Versions: 1.0 Reporter: David Blevins Fix For: 1.1 (Proposed) Ctor injection of e.g. servlets -- 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

[JBoss JIRA] (CDI-175) Support for UEL pluggable type converters

by Pete Muir (Created) (JIRA)

Support for UEL pluggable type converters ----------------------------------------- Key: CDI-175 URL: https://issues.jboss.org/browse/CDI-175 Project: CDI Specification Issues Issue Type: Feature Request Affects Versions: 1.0 Reporter: Pete Muir Priority: Optional Fix For: 1.1 (Proposed) -- 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

[JBoss JIRA] Created: (CDI-144) Support Injection into Entity Listeners

by Cody Lerum (JIRA)

Support Injection into Entity Listeners --------------------------------------- Key: CDI-144 URL: https://issues.jboss.org/browse/CDI-144 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Cody Lerum It would be very convenient if CDI was available inside JPA Entity Listeners. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

6
15
0 / 0

[JBoss JIRA] (CDI-211) Clarify BeanManager.createProducer()

by Jozef Hartinger (JIRA)

Jozef Hartinger created CDI-211: ----------------------------------- Summary: Clarify BeanManager.createProducer() Key: CDI-211 URL: https://issues.jboss.org/browse/CDI-211 Project: CDI Specification Issues Issue Type: Clarification Components: Portable Extensions Affects Versions: 1.1.EDR1 Reporter: Jozef Hartinger Fix For: 1.1 (Proposed) The specification defines a pair of BeanManager.createProducer() methods: {code} public Producer<?> createProducer(AnnotatedField<?> field); public Producer<?> createProducer(AnnotatedMethod<?> method); {code} If cases when the field or method is not static, it is unclear which contextual instance the created producer should operate upon. -- 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
13
0 / 0

[JBoss JIRA] (CDI-190) Require deployment-time validation of injection points defined on observer and disposer methods

by Jozef Hartinger (Created) (JIRA)

Require deployment-time validation of injection points defined on observer and disposer methods ----------------------------------------------------------------------------------------------- Key: CDI-190 URL: https://issues.jboss.org/browse/CDI-190 Project: CDI Specification Issues Issue Type: Feature Request Affects Versions: 1.1.EDR1 Reporter: Jozef Hartinger Fix For: 1.1.EDR2 The spec says: {quote} The container must validate all injection points of all enabled beans and of all other Java EE component classes supporting injection when the application is initialized to ensure that there are no unsatisfied or unresolvable ambiguous dependen- cies. If an unsatisfied or unresolvable ambiguous dependency exists, the container automatically detects the problem and treats it as a deployment problem. {quote} This should be clarified to also include validation of injection points of observer and disposer methods of enabled beans. -- 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-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-244) Allow public static fields on managed beans which declare any other scope than dependent

by Martin Kouba (JIRA)

Martin Kouba created CDI-244: -------------------------------- Summary: Allow public static fields on managed beans which declare any other scope than dependent Key: CDI-244 URL: https://issues.jboss.org/browse/CDI-244 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Martin Kouba See 3.1. Managed beans: {quote} If a managed bean has a public field, it must have scope @Dependent. If a managed bean with a public field declares any scope other than @Dependent, the container automatically detects the problem and treats it as a definition error. {quote} I see no reason why to disallow public _static_ fields on normal scoped beans. To treat public _non-static_ fields as a definition error due to proxy generation is reasonable. However public static fields are usually referenced by the class name and refering to static fields with an object reference (proxy in this case) is discouraged. Moreover, protected and package-private fields which might also cause confusion around proxies are allowed. BTW Weld allows public static fields on normal scoped beans at the moment. Maybe the spec wording could be: {quote} 3.1. Managed beans If a managed bean has a _non-static_ public field, it must have scope @Dependent. If a managed bean with a _non-static_ public field declares any scope other than @Dependent, the container automatically detects the problem and treats it as a definition error. {quote} -- 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
7
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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev July 2012