April 2012 - cdi-dev - Jboss List Archives

[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

12 years, 4 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

12 years, 5 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, 5 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

12 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (CDI-121) TransactionScope

by Richard Hightower (JIRA)

TransactionScope ---------------- Key: CDI-121 URL: https://issues.jboss.org/browse/CDI-121 Project: CDI Specification Issues Issue Type: Feature Request Components: Contexts Affects Versions: 1.1 (Proposed) Environment: Java EE Reporter: Richard Hightower Priority: Minor Add TransctionalScope as a standard scope to define beans whose lifecycle is the same as a given transaction. This scope should start automatically when a transaction starts (but lazily when actually needed). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

14
47
0 / 0

[JBoss JIRA] Created: (CDI-166) Disallow self consuming producers

by Martin Kouba (JIRA)

Disallow self consuming producers --------------------------------- Key: CDI-166 URL: https://issues.jboss.org/browse/CDI-166 Project: CDI Specification Issues Issue Type: Clarification Affects Versions: 1.0 Reporter: Martin Kouba Explicitly dissallow circular dependency in producers. That means bean which declares a producer and injects the result of that producer into the producer is not legal. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

2
6
0 / 0

[JBoss JIRA] (CDI-189) Event qualifiers - empty set

by Jozef Hartinger (Created) (JIRA)

Event qualifiers - empty set ---------------------------- Key: CDI-189 URL: https://issues.jboss.org/browse/CDI-189 Project: CDI Specification Issues Issue Type: Bug Components: Events Affects Versions: 1.1.EDR1, 1.0 Reporter: Jozef Hartinger Priority: Minor Fix For: 1.1.EDR2 The spec says: {quote} An event comprises: * A Java object—the event object * A (*possibly empty*) set of instances of qualifier types—the event qualifiers {quote} while at the same it says that: {quote} *Every* event has the qualifier @javax.enterprise.inject.Any, even if it does not explicitly declare this qualifier. {quote} which impliest that a set of qualifiers of an event cannot be empty. -- 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, 5 months

2
1
0 / 0

[JBoss JIRA] (CDI-192) Unify coding style of the SPI interfaces

by Jozef Hartinger (Created) (JIRA)

Unify coding style of the SPI interfaces ---------------------------------------- Key: CDI-192 URL: https://issues.jboss.org/browse/CDI-192 Project: CDI Specification Issues Issue Type: Bug Components: Portable Extensions Affects Versions: 1.1.EDR1 Reporter: Jozef Hartinger Priority: Trivial Fix For: 1.1 (Proposed) The [JLS|http://java.sun.com/docs/books/jls/third_edition/html/interfaces.html...] says: {quote} For compatibility with older versions of the Java platform, it is permitted but discouraged, as a matter of style, to redundantly specify the abstract modifier for methods declared in interfaces. It is permitted, but strongly discouraged as a matter of style, to redundantly specify the public modifier for interface methods. {quote} The vast majority of CDI API interfaces specifies the public modifier while leaving out the abstract modifier, however, there are exceptions: {code:JAVA} public interface Context { ... boolean isActive(); } {code} {code:JAVA} public interface BeanAttributes<T> { public abstract Set<Type> getTypes(); public abstract Set<Annotation> getQualifiers(); ... {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, 5 months

2
1
0 / 0

[JBoss JIRA] (CDI-209) BeanManager.createProducer missing in the API

by Jozef Hartinger (JIRA)

Jozef Hartinger created CDI-209: ----------------------------------- Summary: BeanManager.createProducer missing in the API Key: CDI-209 URL: https://issues.jboss.org/browse/CDI-209 Project: CDI Specification Issues Issue Type: Bug Components: Portable Extensions Affects Versions: 1.1.EDR1 Reporter: Jozef Hartinger Fix For: 1.1 (Proposed) The spec says: {quote} The method BeanManager.createProducer() returns a container provided implementation of Producer for a given AnnotatedMethod or AnnotatedField or throws an IllegalArgumentException if there is a definition error associated with the producer method or field. {quote} However, the createProducer() method is not defined in the API. -- 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, 5 months

2
1
0 / 0

[JBoss JIRA] (CDI-199) Mean to observe or intercept Conversation.begin

by Anthony O. (Created) (JIRA)

Mean to observe or intercept Conversation.begin ----------------------------------------------- Key: CDI-199 URL: https://issues.jboss.org/browse/CDI-199 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Anthony O. As Pete Muir suggested me in that [stackoverflow question|http://stackoverflow.com/questions/8340676/how-to-observe-or-int...], I'm asking here the possibility of observing or intercepting {{Conversation.begin}} method calls (or other methods on the {{Conversation}} object), event if it's a built-in bean. Has this already been the subject of a debate ? -- 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, 5 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev April 2012