February 2013 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-270) Allow @WithAnnotations to be applied to other events

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-270?page=com.atlassian.jira.plugin.sy... ] Pete Muir updated CDI-270: -------------------------- Fix Version/s: TBD (was: 1.1 (Proposed)) > Allow @WithAnnotations to be applied to other events > ---------------------------------------------------- > > Key: CDI-270 > URL: https://issues.jboss.org/browse/CDI-270 > Project: CDI Specification Issues > Issue Type: Bug > Affects Versions: 1.1.EDR > Reporter: Pete Muir > Labels: with-annotations > Fix For: TBD > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (CDI-316) Adopt usage of the @since Javadoc tag

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-316?page=com.atlassian.jira.plugin.sy... ] Pete Muir updated CDI-316: -------------------------- Fix Version/s: 1.1.PFD (was: 1.1 (Proposed)) > Adopt usage of the @since Javadoc tag > ------------------------------------- > > Key: CDI-316 > URL: https://issues.jboss.org/browse/CDI-316 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Javadoc and API > Affects Versions: 1.1.PRD > Reporter: George Gastaldi > Fix For: 1.1.PFD > > > It's a good practice to use the @since javadoc tag in the methods and interfaces/classes created in this new version. > This is necessary when one need to figure out if some feature is targeted to work in 1.1 only, for example. > This issue was created so that all the API code can be reviewed before the next release. Some classes already have this information, other still don't (@Vetoed is one that is missing, afaik) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (CDI-291) Clarify interceptor/decorator resolution rules

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-291?page=com.atlassian.jira.plugin.sy... ] Pete Muir updated CDI-291: -------------------------- Fix Version/s: 1.1.PFD (was: 1.1 (Proposed)) > Clarify interceptor/decorator resolution rules > ---------------------------------------------- > > Key: CDI-291 > URL: https://issues.jboss.org/browse/CDI-291 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Decorators, Interceptors > Affects Versions: 1.0 > Reporter: Jozef Hartinger > Assignee: Pete Muir > Fix For: 1.1.PFD > > > Currently the spec only says: > {quote} > A decorator is bound to a bean if: > * The bean is assignable to the delegate injection point according to the rules defined in Section 5.2, "Typesafe resolu- > tion" (using Section 8.3.1, "Assignability of raw and parameterized types for delegate injection points"). > * The decorator is enabled in the bean archive containing the bean. > {quote} > AND > {quote} > An interceptor is bound to a method if: > * The method has all the interceptor bindings of the interceptor. A method has an interceptor binding of an interceptor if > it has an interceptor binding with (a) the same type and (b) the same annotation member value for each member which > is not annotated @javax.enterprise.util.Nonbinding. > * The interceptor intercepts the given kind of lifecycle callback or business method. > * The interceptor is enabled in the bean archive containing the bean. > {quote} > What remains unspecified is: > * In a scenario where a module A enables interceptor X in its beans.xml, does X have to be accessible from A. That effectively means that an EJB jar could (or could not) legally use an interceptor/decorator packaged in a web application. > * Even if X is accessible, does it have to be packaged in a bean archive or is it enough for it to be packaged in a library that does not contain beans.xml but is accessible from A? This means that a CDI implementation would need to additionally scan those classes as they would not be scanned by normal bean archive discovery. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (CDI-308) Things with a container assigned priority should start at 1500, not 1000

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-308?page=com.atlassian.jira.plugin.sy... ] Pete Muir resolved CDI-308. --------------------------- Assignee: Pete Muir Fix Version/s: 1.1.PFD (was: 1.1 (Proposed)) Resolution: Rejected This has moved to the interceptors spec > Things with a container assigned priority should start at 1500, not 1000 > ------------------------------------------------------------------------ > > Key: CDI-308 > URL: https://issues.jboss.org/browse/CDI-308 > Project: CDI Specification Issues > Issue Type: Feature Request > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1.PFD > > > This allows easy insertion before -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (CDI-306) Clarify that MDBs don't need to support injected constructors

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-306?page=com.atlassian.jira.plugin.sy... ] Pete Muir updated CDI-306: -------------------------- Fix Version/s: 1.1.PFD (was: 1.1 (Proposed)) > Clarify that MDBs don't need to support injected constructors > ------------------------------------------------------------- > > Key: CDI-306 > URL: https://issues.jboss.org/browse/CDI-306 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Java EE integration > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: 1.1.PFD > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (CDI-311) Move CDI interceptors chapter to interceptors spec

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-311?page=com.atlassian.jira.plugin.sy... ] Pete Muir resolved CDI-311. --------------------------- Assignee: Pete Muir Fix Version/s: 1.1.PFD (was: 1.1 (Proposed)) Resolution: Done The bulk has moved. CDI needs updating to take account of this. > Move CDI interceptors chapter to interceptors spec > -------------------------------------------------- > > Key: CDI-311 > URL: https://issues.jboss.org/browse/CDI-311 > Project: CDI Specification Issues > Issue Type: Feature Request > Affects Versions: 1.1.PRD > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1.PFD > > > The Java EE spec leads have requested that we align by moving this chapter over to the interceptors spec as an optional way of using interceptors, that is required for CDI beans. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (CDI-305) Reflect the new EJB passivation-capable flag in CDI

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-305?page=com.atlassian.jira.plugin.sy... ] Pete Muir updated CDI-305: -------------------------- Fix Version/s: 1.1.PFD (was: 1.1 (Proposed)) > Reflect the new EJB passivation-capable flag in CDI > --------------------------------------------------- > > Key: CDI-305 > URL: https://issues.jboss.org/browse/CDI-305 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration > Affects Versions: 1.1.PRD > Reporter: Pete Muir > Fix For: 1.1.PFD > > > EJB 3.2 adds the ability to disable passivation of SFSB by either using @Stateful(passivationCapable=false) or setting it in the DD. > We should update the CDI spec to cover this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (CDI-303) Clarify declaring selected alternatives for an application

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-303?page=com.atlassian.jira.plugin.sy... ] Pete Muir updated CDI-303: -------------------------- Fix Version/s: 1.1.PFD (was: 1.1 (Proposed)) > Clarify declaring selected alternatives for an application > ---------------------------------------------------------- > > Key: CDI-303 > URL: https://issues.jboss.org/browse/CDI-303 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Martin Kouba > Fix For: 1.1.PFD > > > It's not clear whether an alternative with a default priority but not selected for an application is selected for the bean archive whose beans.xml declares it. > The spec states: > {quote} > An alternative may be given a default priority, but not selected for an application using the <alternatives> element of the beans.xml file of the bean archive. The <alternatives> element contains a list of bean classes and stereotypes, along with a disabled flag and a priority attribute. An alternative is selected for the bean archive if either: > ... > {quote} > Pay attention to the last sentence of the paragraph. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (CDI-309) Consider using -1 as a priority to disable something rather than an explicit enabled flag

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-309?page=com.atlassian.jira.plugin.sy... ] Pete Muir resolved CDI-309. --------------------------- Assignee: Pete Muir Fix Version/s: 1.1.PFD (was: 1.1 (Proposed)) Resolution: Out of Date This has been moved to the interceptors spec and resolved there > Consider using -1 as a priority to disable something rather than an explicit enabled flag > ----------------------------------------------------------------------------------------- > > Key: CDI-309 > URL: https://issues.jboss.org/browse/CDI-309 > Project: CDI Specification Issues > Issue Type: Feature Request > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1.PFD > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (CDI-310) Standardize priority range size to 1000 a piece

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-310?page=com.atlassian.jira.plugin.sy... ] Pete Muir resolved CDI-310. --------------------------- Assignee: Pete Muir Fix Version/s: 1.1.PFD (was: 1.1 (Proposed)) Resolution: Out of Date This has been moved to the interceptors spec and resolved. > Standardize priority range size to 1000 a piece > ----------------------------------------------- > > Key: CDI-310 > URL: https://issues.jboss.org/browse/CDI-310 > Project: CDI Specification Issues > Issue Type: Feature Request > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1.PFD > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev February 2013