July 2012 - cdi-dev - Jboss List Archives

[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

11 years, 8 months

2
4
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

11 years, 8 months

4
6
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

11 years, 8 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

11 years, 8 months

2
4
0 / 0

[JBoss JIRA] (CDI-231) Clarify if Alternatives are filtered in BeanManager#getBeans() or #resolve()

by Mark Struberg (JIRA)

Mark Struberg created CDI-231: --------------------------------- Summary: Clarify if Alternatives are filtered in BeanManager#getBeans() or #resolve() Key: CDI-231 URL: https://issues.jboss.org/browse/CDI-231 Project: CDI Specification Issues Issue Type: Clarification Components: Resolution Affects Versions: 1.1.EDR1, 1.0 Reporter: Mark Struberg Assignee: Mark Struberg Fix For: 1.1 (Proposed) The spec and javadoc are not really clear if the @Alternative filter defined in "5.2.1. Unsatisfied and ambiguous dependencies" is already performed in BeanManager#getBeans() or only later in BeanManager#resolve(). Back in 2009 I did a blind test with an old Weld version which only returned @Alternatives in getBeans() and all other beans got filtered out. This seems to have changed now (since quite some time). Can we make this more clear what should happen in getBeans() and what should happen in resolve()? -- 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

11 years, 8 months

4
8
0 / 0

[JBoss JIRA] (CDI-240) Add javadoc comment for ProcessSessionBean type parameter

by Martin Kouba (JIRA)

Martin Kouba created CDI-240: -------------------------------- Summary: Add javadoc comment for ProcessSessionBean type parameter Key: CDI-240 URL: https://issues.jboss.org/browse/CDI-240 Project: CDI Specification Issues Issue Type: Bug Components: Javadoc and API Reporter: Martin Kouba Priority: Minor Also add clarification why ProcessSessionBean type declaration is {{ProcessSessionBean<X> extends ProcessManagedBean<Object>}} and not {{ProcessSessionBean<X> extends ProcessManagedBean<X>}}. See also: http://lists.jboss.org/pipermail/cdi-dev/2012-July/001914.html -- 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

11 years, 8 months

2
4
0 / 0

[JBoss JIRA] (CDI-222) Reword inheritance of member-level metadata for generic beans

by Martin Kouba (JIRA)

Martin Kouba created CDI-222: -------------------------------- Summary: Reword inheritance of member-level metadata for generic beans Key: CDI-222 URL: https://issues.jboss.org/browse/CDI-222 Project: CDI Specification Issues Issue Type: Clarification Reporter: Martin Kouba Priority: Minor See *4.2. Inheritance of member-level metadata*: "If X is a generic type, and an injection point, producer method, producer field, disposer method or observer method declared by X is inherited by Y..." Since non-static producer method, producer field and disposer method +*are not inherited*+, this paragraph should be reworded in this way: "If X is a generic type, and an injection point or observer method declared by X is inherited by Y..." -- 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

11 years, 8 months

3
7
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

11 years, 8 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

11 years, 8 months

2
1
0 / 0

[JBoss JIRA] (CDI-198) Make beans.xml validation consistent with the ProcessModule event

by Jozef Hartinger (Created) (JIRA)

Make beans.xml validation consistent with the ProcessModule event ----------------------------------------------------------------- Key: CDI-198 URL: https://issues.jboss.org/browse/CDI-198 Project: CDI Specification Issues Issue Type: Feature Request Components: Portable Extensions Affects Versions: 1.1.EDR1 Reporter: Jozef Hartinger Fix For: 1.1 (Proposed) The validation of enabled interceptors, alternatives and decorators is currently tightly related to the beans.xml file, e.g.: {quote}If the same class is listed twice under the <interceptors> element, the container automatically detects the problem and treats it as a deployment problem.{quote} With CDI-97 in place, which allows extensions to change the enabled alternatives, decorators and interceptors, this is no longer sufficient. IMO, the validation of enabled interceptors and decorators should be the following: 1.) For each deployment descriptor, the container verifies that it does not contain duplicate interceptors, decorators or alternatives. 2.) For each BDA, the container fires the ProcessModule event allowing extensions to modify enabled alternatives, interceptors and decorators. 3.) For each BDA, the container verifies that the resulting collection of enabled alternatives, decorators and interceptors does not contain duplicates. The step 1.) is not actually necessary but may be convenient. -- 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

11 years, 8 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev July 2012