January 2011 - cdi-dev - Jboss List Archives

[JBoss JIRA] Updated: (CDI-11) cdi-api lists el-api as optional in pom, but is required by api

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-11?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-11: ------------------------- Fix Version/s: TBD > cdi-api lists el-api as optional in pom, but is required by api > --------------------------------------------------------------- > > Key: CDI-11 > URL: https://issues.jboss.org/browse/CDI-11 > Project: CDI Specification Issues > Issue Type: Bug > Components: Javadoc and API > Affects Versions: 1.0 > Reporter: Aslak Knutsen > Fix For: TBD > > > ElResolver from el-api is a part of cdi-api's BeanManager interface, but the cdi-api pom lists el-api as optional. > http://repo2.maven.org/maven2/javax/enterprise/cdi-api/1.0-SP1/cdi-api-1.... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-84) Non EE modules should be able to trigger creation of a BeanManager

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-84?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-84: ------------------------- Fix Version/s: TBD > Non EE modules should be able to trigger creation of a BeanManager > ------------------------------------------------------------------ > > Key: CDI-84 > URL: https://issues.jboss.org/browse/CDI-84 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration, Packaging and Deployment > Affects Versions: 1.0 > Reporter: Aslak Knutsen > Fix For: TBD > > > EE.5.19 > A bean manager is only available in modules in which CDI has been enabled. > Where EE modules are defined to be; ejb-jar, rar, client jar and war. > This is a missmatch between the EE spec and the CDI spec. According to the CDI spec, any archive with a beans.xml is defined as a BeanArchive and should be included in a BeanManager, EE define it to be only EE modules should trigger BeanManager creation. > Opening this up to follow the CDI spec will let any library use the BeanManager to introspect other BeanArchives without having to involve the owning EE module in the loop. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-13) Add ability to inject InjectionPoint into a decorator

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-13?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-13: ------------------------- Fix Version/s: TBD > Add ability to inject InjectionPoint into a decorator > ----------------------------------------------------- > > Key: CDI-13 > URL: https://issues.jboss.org/browse/CDI-13 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Decorators > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: TBD > > > The idea here is that it would allow you inspect the decorator stack -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-48) Global Interceptor/Decorator ordering

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-48?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-48: ------------------------- Fix Version/s: TBD > Global Interceptor/Decorator ordering > ------------------------------------- > > Key: CDI-48 > URL: https://issues.jboss.org/browse/CDI-48 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Decorators, Interceptors, Packaging and Deployment > Affects Versions: 1.0 > Reporter: Stuart Douglas > Fix For: TBD > > > Currently interceptor/decorator ordering is specified on a per bean archive level. In the majority of cases the correct ordering is the same for every BDA in the application, so this violates DRY and opens the door to nasty bugs due to different ordering per module if beans.xml files get out of sync. > We should look at allowing the user to define interceptor and decorator ordering once per app and have this applied to all modules in the deployment. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-76) JavaDocs regarding adding scopes are weak

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-76?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-76: ------------------------- Fix Version/s: TBD > JavaDocs regarding adding scopes are weak > ----------------------------------------- > > Key: CDI-76 > URL: https://issues.jboss.org/browse/CDI-76 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Javadoc and API, Portable Extensions > Affects Versions: 1.0 > Reporter: Lincoln Baxter III > Fix For: TBD > > > JavaDocs for adding scopes via the eventing API are a bit weak. > public void addScope(@Observes final BeforeBeanDiscovery event) > { > event.addScope(ProjectScoped.class, true, false); > } > Currently it is not clear that using this method is only required when not using the @NormalScoped annotation, and that it will in fact override the annotation if present. Additional docs should probably be placed on both sides of this relationship, to that affect. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-39) Add a standard format for defining metadata about extensions

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-39?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-39: ------------------------- Fix Version/s: TBD > Add a standard format for defining metadata about extensions > ------------------------------------------------------------ > > Key: CDI-39 > URL: https://issues.jboss.org/browse/CDI-39 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Portable Extensions > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: TBD > > > e.g. add optional name, description and version fields to an optional annotation. Makes it easy for modules to track what is being loaded -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-92) Allow injection of Bean object for a bean

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-92?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-92: ------------------------- Fix Version/s: TBD > Allow injection of Bean object for a bean > ----------------------------------------- > > Key: CDI-92 > URL: https://issues.jboss.org/browse/CDI-92 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: TBD > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-32) A method of controlling event ordering

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-32?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-32: ------------------------- Fix Version/s: TBD > A method of controlling event ordering > -------------------------------------- > > Key: CDI-32 > URL: https://issues.jboss.org/browse/CDI-32 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Events > Affects Versions: 1.0 > Reporter: Nicklas Karlsson > Fix For: TBD > > > It would be handy to have a way of controlling the order in which synchronous events are being called -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-4) Need a way to provide ordering for Event observers (@Observes)

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-4?page=com.atlassian.jira.plugin.syst... ] Pete Muir updated CDI-4: ------------------------ Fix Version/s: TBD > Need a way to provide ordering for Event observers (@Observes) > -------------------------------------------------------------- > > Key: CDI-4 > URL: https://issues.jboss.org/browse/CDI-4 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Events, Portable Extensions > Affects Versions: 1.0 > Environment: All > Reporter: Lincoln Baxter III > Fix For: TBD > > > There needs to be a way to specify some kind of ordering for Event observers. > Understandably, this is somewhat counter-intuitive to the general concept of observing an event, but there is going to be need for this in an upcoming JBoss project. While it can be done manually, it might be nice to have a built-in API. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-79) Allow you to inspect the decorator chain

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-79?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-79: ------------------------- Fix Version/s: TBD > Allow you to inspect the decorator chain > ---------------------------------------- > > Key: CDI-79 > URL: https://issues.jboss.org/browse/CDI-79 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Decorators > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: TBD > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev January 2011