October 2012 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-265) Specify the @Initialized(ApplicationScoped.class) event payload for an EAR with multiple WARs

by Martin Kouba (JIRA)

Martin Kouba created CDI-265: -------------------------------- Summary: Specify the @Initialized(ApplicationScoped.class) event payload for an EAR with multiple WARs Key: CDI-265 URL: https://issues.jboss.org/browse/CDI-265 Project: CDI Specification Issues Issue Type: Clarification Affects Versions: 1.1.EDR Reporter: Martin Kouba The spec states: {quote} The event payload is: * the ServletContextEvent if the application is a web application deployed to a Servlet container, or * ... {quote} However this will not work for enterprise archives with multiple web modules (which ServletContextEvent would be the payload). -- 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

12 years, 1 month

3
5
0 / 0

[JBoss JIRA] (CDI-247) It's currently not possible to implement a primitive and wrapping type producer method for the same type

by Mark Struberg (JIRA)

Mark Struberg created CDI-247: --------------------------------- Summary: It's currently not possible to implement a primitive and wrapping type producer method for the same type Key: CDI-247 URL: https://issues.jboss.org/browse/CDI-247 Project: CDI Specification Issues Issue Type: Bug Components: Concepts Affects Versions: 1.1.EDR1, 1.0 Reporter: Mark Struberg 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, 1 month

5
13
0 / 0

[JBoss JIRA] (CDI-234) behavior of arrays without @Nonbinding

by Romain Manni-Bucau (JIRA)

Romain Manni-Bucau created CDI-234: -------------------------------------- Summary: behavior of arrays without @Nonbinding Key: CDI-234 URL: https://issues.jboss.org/browse/CDI-234 Project: CDI Specification Issues Issue Type: Clarification Reporter: Romain Manni-Bucau The spec says: "Array-valued or annotation-valued members of a qualifier type should be annotated @Nonbinding in a portable application. If an array-valued or annotation-valued member of a qualifier type is not annotated @Nonbinding, non-portable behavior results." The case of arrays without this annotation should be managed to get a better portability. Two arraysequality is determined through "Arrays" helper (http://docs.oracle.com/javase/1.5.0/docs/api/java/lang/annotation/Annotat...) so i don't think there is any technical issue to consider arrays as a field. -- 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, 1 month

3
21
0 / 0

[JBoss JIRA] (CDI-225) Clarify whether bean discovery MAY or MUST NOT include class loading

by Harald Wellmann (JIRA)

Harald Wellmann created CDI-225: ----------------------------------- Summary: Clarify whether bean discovery MAY or MUST NOT include class loading Key: CDI-225 URL: https://issues.jboss.org/browse/CDI-225 Project: CDI Specification Issues Issue Type: Clarification Components: Resolution Affects Versions: 1.1.EDR1 Reporter: Harald Wellmann The CDI 1.0 spec and also the current 1.1 draft is rather vague about the issue of class loading vs. class file byte code scanning for bean discovery. By default, I would assume the term "class" in a specification to refer to a loaded class, unless explicitly stated otherwise. A feature like Seam Solder's {code} @Requires(OptionalDependency.class) public class OptionalBean {code} will necessarily break if the CDI container loads OptionalBean during bean discovery - when OptionalDepencency is not available, OptionalBean cannot be loaded, and the CDI container won't even see the @Requires annotation. See also http://seamframework.org/Seam3/Compatibility, Section Overzealous class scanner. The way I read the CDI spec, GlassFish is fully spec compliant (but maybe not very efficient) in loading bean archive classes for the purpose of discovery. @Requires is also spec compliant, but not portable because it tacitly assumes that classes get scanned but not loaded. So if scanning in place of loading has been a tacit assumption of the CDI 1.0 authors all the time, it should be made explicit in CDI 1.1. Otherwise, if loading is also a valid option, this should be clearly stated so that extension authors will not rely on accidental features of a given CDI implementation. -- 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, 1 month

3
5
0 / 0

[JBoss JIRA] (CDI-259) Add conversation begin and conversation end events

by Pete Muir (JIRA)

Pete Muir created CDI-259: ----------------------------- Summary: Add conversation begin and conversation end events Key: CDI-259 URL: https://issues.jboss.org/browse/CDI-259 Project: CDI Specification Issues Issue Type: Feature Request Affects Versions: 1.1.EDR Reporter: Pete Muir Fix For: 1.1 (Proposed) -- 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

12 years, 1 month

2
3
0 / 0

[JBoss JIRA] (CDI-229) introduce @OverridesAttribute for @StereoType

by Mark Struberg (JIRA)

Mark Struberg created CDI-229: --------------------------------- Summary: introduce @OverridesAttribute for @StereoType Key: CDI-229 URL: https://issues.jboss.org/browse/CDI-229 Project: CDI Specification Issues Issue Type: Feature Request Components: Beans Affects Versions: 1.1.EDR1 Reporter: Mark Struberg We recently had a thread on the DeltaSpike list about using StereoTypes in real world applications: http://markmail.org/thread/uqozhsix2znwiebn ------ Imagine the following Stereotype for my Services (I spare out the standard stuff) @StereoType @Secured @Transactional @ApplicationScoped public @interface @Service {} The problem here is that there is no way to 'propagate' any rolesAllowed from @Service to @Secured, etc. What I'd like to have is something like ... public @interface @Service { String[] rolesAllowed(); TransactionAttributeType transactionType(); } where the rolesAllowed() would get propagated to the @Secured meta-annotation and transactionType() to the @Transactional ----------- Gerhard Petracek now pointed me to a cool feature which is used in JSR-303 BVAL: @OverridesAttribute http://docs.oracle.com/javaee/6/api/javax/validation/OverridesAttribute.html We should ping the BVAL EG for the details. There are quite a few little tricks and side effects to consider. On the implementation side, we could e.g. pick the @StereoType annotation and automatically propagate those values to the AnnotatedType which get's passed to the Extensions -- 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, 1 month

5
7
0 / 0

[JBoss JIRA] (CDI-277) Clarify inheritance behavior of observer methods

by Arne Limburg (JIRA)

Arne Limburg created CDI-277: -------------------------------- Summary: Clarify inheritance behavior of observer methods Key: CDI-277 URL: https://issues.jboss.org/browse/CDI-277 Project: CDI Specification Issues Issue Type: Clarification Reporter: Arne Limburg -- 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

12 years, 2 months

5
23
0 / 0

[JBoss JIRA] (CDI-276) Clarify that scope annotations shouldn't be used at injection points

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-276?page=com.atlassian.jira.plugin.sy... ] Pete Muir commented on CDI-276: ------------------------------- But understood that it is a problem, I just think we need to think up something that isn't restrictive but still helpful. > Clarify that scope annotations shouldn't be used at injection points > -------------------------------------------------------------------- > > Key: CDI-276 > URL: https://issues.jboss.org/browse/CDI-276 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Contexts > Reporter: Nicklas Karlsson > Fix For: 1.1 (Proposed) > > > Sometimes you see people trying to do > @Inject @ApplicationScoped > private SomeRequestScopedBean sRSB; > It should be clarified that this has no effect. Could even throw a validation exception at deployment. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-276) Clarify that scope annotations shouldn't be used at injection points

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-276?page=com.atlassian.jira.plugin.sy... ] Pete Muir commented on CDI-276: ------------------------------- The issue with this one is that someone might want to define an extension that did allow this... > Clarify that scope annotations shouldn't be used at injection points > -------------------------------------------------------------------- > > Key: CDI-276 > URL: https://issues.jboss.org/browse/CDI-276 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Contexts > Reporter: Nicklas Karlsson > Fix For: 1.1 (Proposed) > > > Sometimes you see people trying to do > @Inject @ApplicationScoped > private SomeRequestScopedBean sRSB; > It should be clarified that this has no effect. Could even throw a validation exception at deployment. -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-3) Add add an event that fires after all ProcessAnnotatedType events that allows you to add new AnnotatedTypes

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-3?page=com.atlassian.jira.plugin.syst... ] Pete Muir updated CDI-3: ------------------------ Priority: Critical (was: Major) Increasing the priority, as [~struberg] and [~jharting] pointed out, if you can alter annotations it's critical that this is done before beans start being defined. > Add add an event that fires after all ProcessAnnotatedType events that allows you to add new AnnotatedTypes > ------------------------------------------------------------------------------------------------------------ > > Key: CDI-3 > URL: https://issues.jboss.org/browse/CDI-3 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Portable Extensions > Affects Versions: 1.0 > Reporter: Stuart Douglas > Priority: Critical > Fix For: 1.1 (Proposed) > > > At the moment AnnotatedTypes can only be added in the BeforeBeanDiscovery phase. This means that if you want to install additional beans based on the beans processed in the ProcessAnnotatedType phase you must instead add implementations of the Bean interface in the AfterBeanDiscovery phase. This interface is more limited than annotated type, and does not let you exactly mimic the behaviour of beans added as AnnotatedTypes. > Some of the things that the bean interface will not let you mimic are: > - Interceptors > - Disposal methods > - Producer fields for normal scoped 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

12 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev October 2012