November 2011 - cdi-dev - Jboss List Archives

[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

[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

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

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

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

11 years, 8 months

2
1
0 / 0

[JBoss JIRA] (CDI-196) Related to web_beans-1_0-fr-spec.pdf for using CDI, section 5.2.4. Primitive types and null values.

by Shruthi Nanjundaswamy (Created) (JIRA)

Related to web_beans-1_0-fr-spec.pdf for using CDI, section 5.2.4. Primitive types and null values. --------------------------------------------------------------------------------------------------- Key: CDI-196 URL: https://issues.jboss.org/browse/CDI-196 Project: CDI Specification Issues Issue Type: Clarification Components: Contexts Reporter: Shruthi Nanjundaswamy -- 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
2
0 / 0

[JBoss JIRA] (CDI-191) ProcessSyntheticAnnotatedType not public

by Jozef Hartinger (Created) (JIRA)

ProcessSyntheticAnnotatedType not public ---------------------------------------- Key: CDI-191 URL: https://issues.jboss.org/browse/CDI-191 Project: CDI Specification Issues Issue Type: Bug Components: Portable Extensions Affects Versions: 1.1.EDR1 Reporter: Jozef Hartinger Assignee: Pete Muir Priority: Blocker Fix For: 1.1 (Proposed) {code:JAVA} interface ProcessSyntheticAnnotatedType<X> extends ProcessAnnotatedType<X> { public Extension getSource(); } {code} ProcessSyntheticAnnotatedType is not public. As a result, it is pretty difficult to implement. -- 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-52) Make it clearer that an InjectionPoint injected into a disposer method refers to the producer method bean and not to the declaring bean

by Jozef Hartinger (Commented) (JIRA)

[ https://issues.jboss.org/browse/CDI-52?page=com.atlassian.jira.plugin.sys... ] Jozef Hartinger commented on CDI-52: ------------------------------------ Also, a disposer method may be bound into multiple producer fields/methods. The specification should specify what happens, if the disposer method has an InjectionPoint parameters and any of the producer fields/methods the disposer method is bound to is not @Dependent. > Make it clearer that an InjectionPoint injected into a disposer method refers to the producer method bean and not to the declaring bean > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: CDI-52 > URL: https://issues.jboss.org/browse/CDI-52 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Beans > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1.EDR2 > > -- 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

1
0
0 / 0

[JBoss JIRA] (CDI-78) Clarify how isDelegate() behaves on InjectionPoint, and what happens when an InjectionPoint is injected into a Decorator

by Jozef Hartinger (Reopened) (JIRA)

[ https://issues.jboss.org/browse/CDI-78?page=com.atlassian.jira.plugin.sys... ] Jozef Hartinger reopened CDI-78: -------------------------------- Reopening for multiple reasons: * the issue aims to make two clarifications but one of those, that isDelegate() always returns false for an injected InjectionPoint, is not present in the specification * a change in the specification now allows InjectionPoint to be injected into a decorator but does not state what happens if a decorated component is not @Dependent. > Clarify how isDelegate() behaves on InjectionPoint, and what happens when an InjectionPoint is injected into a Decorator > ------------------------------------------------------------------------------------------------------------------------ > > Key: CDI-78 > URL: https://issues.jboss.org/browse/CDI-78 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Decorators > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1.EDR1 > > > The InjectionPoint should be that of the injection into the consumer, and isDelegate() should return false. -- 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

1
0
0 / 0

[JBoss JIRA] (CDI-50) Ability to veto beans, both unconditionally and based on classes visible

by Arne Limburg (Commented) (JIRA)

[ https://issues.jboss.org/browse/CDI-50?page=com.atlassian.jira.plugin.sys... ] Arne Limburg commented on CDI-50: --------------------------------- Vinicius, your requirement could be met with the Instance<CacheService> which was designed for that use case. > Ability to veto beans, both unconditionally and based on classes visible > ------------------------------------------------------------------------ > > Key: CDI-50 > URL: https://issues.jboss.org/browse/CDI-50 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Concepts, Packaging and Deployment > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1.EDR2 > > > This should support both a straight veto, and conditional based on classes available. > Seam Solder supports this as @Veto and @Requires({Foo.class, Bar.class}). > Mark Struberg proposed using @Optional -- 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev November 2011