September 2011 - cdi-dev - Jboss List Archives

[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: 1.1 (Confirmed) (was: 1.1 (Proposed)) Git Pull Request: https://github.com/jboss/cdi/pull/53 (was: https://github.com/jboss/cdi/pull/53) Forum Reference: http://www.seamframework.org/Weld/DependencyInjectionWishlist#H-AllowInje... (was: http://www.seamframework.org/Weld/DependencyInjectionWishlist#H-AllowInje...) > 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: 1.1 (Confirmed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (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 commented on CDI-3: ----------------------------- Updated proposal is to clarify that BBD should occur after all classes are discovered and before beans are discovered. A search of all Seam and Errai code revealed that this wouldn't break anything. Anyone else got any concerns? We would also add a BeforeTypeDiscovery event that would occur after modules are discovered and before types are discovered, and potentially a BeforeModuleDiscovery event. > 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 > 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. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 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: ------------------------- Git Pull Request: https://github.com/jboss/cdi/pull/53 Forum Reference: http://www.seamframework.org/Weld/DependencyInjectionWishlist#H-AllowInje... (was: http://www.seamframework.org/Weld/DependencyInjectionWishlist#H-AllowInje...) > 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: 1.1 (Proposed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (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 commented on CDI-92: ------------------------------ https://github.com/jboss/cdi/pull/53 > 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: 1.1 (Proposed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (CDI-23) Allow BeanManager to be resolved as though you were in another bean archive

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-23?page=com.atlassian.jira.plugin.sys... ] Pete Muir closed CDI-23. ------------------------ Assignee: Pete Muir Resolution: Partially Completed This has been merged into CDI-101 > Allow BeanManager to be resolved as though you were in another bean archive > --------------------------------------------------------------------------- > > Key: CDI-23 > URL: https://issues.jboss.org/browse/CDI-23 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Portable Extensions, Resolution > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1 (Proposed) > > > Currently it's not possible to access beans as though you were in another bean manager, something that is useful for extensions to be able to do. For example, if I want to create a facade over the ELResolver, or access a particular configuration bean. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (CDI-101) Use Module object, instead of Class for inter-module dependency resolution

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-101?page=com.atlassian.jira.plugin.sy... ] Pete Muir commented on CDI-101: ------------------------------- At the same time, cover CDI-23, and require the BeanManager injected into a ProcessModule event to follow the dependency resolution rules for that module. > Use Module object, instead of Class for inter-module dependency resolution > -------------------------------------------------------------------------- > > Key: CDI-101 > URL: https://issues.jboss.org/browse/CDI-101 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Portable Extensions > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: 1.1 (Proposed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

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

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-50?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-50: ------------------------- Git Pull Request: https://github.com/jboss/cdi/pull/52 Forum Reference: http://lists.jboss.org/pipermail/weld-dev/2009-December/002029.html (was: http://lists.jboss.org/pipermail/weld-dev/2009-December/002029.html) > 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 > Fix For: 1.1 (Proposed) > > > 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. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-59) Clarify interceptors/decorators aren't applied to the *result* of a producer method or producer field

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-59?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-59: ------------------------- Summary: Clarify interceptors/decorators aren't applied to the *result* of a producer method or producer field (was: Clarify that interceptors/decorators don't apply to producers in resolution rules) Description: Interceptors can be applied to the invocation of a producer method, but not to a bean produced by a producer method. Decorators cannot be applied I wonder if decorators should be applied? If so, let's spin it out as a feature request. > Clarify interceptors/decorators aren't applied to the *result* of a producer method or producer field > ----------------------------------------------------------------------------------------------------- > > Key: CDI-59 > URL: https://issues.jboss.org/browse/CDI-59 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Beans, Decorators, Interceptors, Resolution > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Marius Bogoevici > Priority: Minor > Fix For: 1.1 (Proposed) > > > Interceptors can be applied to the invocation of a producer method, but not to a bean produced by a producer method. Decorators cannot be applied -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (CDI-60) In lifecycle chapter, clarify creation of interceptors/decorator

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-60?page=com.atlassian.jira.plugin.sys... ] Pete Muir closed CDI-60. ------------------------ Assignee: Pete Muir (was: Marius Bogoevici) Fix Version/s: (was: 1.1 (Proposed)) Resolution: Rejected No idea what I wanted here :-( > In lifecycle chapter, clarify creation of interceptors/decorator > ---------------------------------------------------------------- > > Key: CDI-60 > URL: https://issues.jboss.org/browse/CDI-60 > Project: CDI Specification Issues > Issue Type: Bug > Components: Decorators, Interceptors > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Priority: Minor > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (CDI-1) Clarify how resource producer fields (for persistence contexts) interact with transaction propagation

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-1?page=com.atlassian.jira.plugin.syst... ] Pete Muir commented on CDI-1: ----------------------------- Add a note to clarify that the PC's should propagate as defined by JPA specs. Stuart if I do this, is it sufficient from your understanding? > Clarify how resource producer fields (for persistence contexts) interact with transaction propagation > ----------------------------------------------------------------------------------------------------- > > Key: CDI-1 > URL: https://issues.jboss.org/browse/CDI-1 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Java EE integration > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: 1.1 (Proposed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev September 2011