January 2011 - cdi-dev - Jboss List Archives

[JBoss JIRA] Updated: (CDI-33) fire ProcessAnnotatedType for AnnotatedTypes added via BBD.addAnnotatedType()

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-33?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-33: ------------------------- Fix Version/s: TBD > fire ProcessAnnotatedType for AnnotatedTypes added via BBD.addAnnotatedType() > ----------------------------------------------------------------------------- > > Key: CDI-33 > URL: https://issues.jboss.org/browse/CDI-33 > Project: CDI Specification Issues > Issue Type: Task > Components: Portable Extensions > Affects Versions: 1.0 > Reporter: Jozef Hartinger > Fix For: TBD > > > Currently, the ProcessAnnotatedType event is fired for AnnotatedTypes discovered in a BDA only. However, portable extensions are allowed to register other AnnotatedTypes using addAnnotatedType() during the BeforeBeanDiscovery phase. For these AnnotatedTypes, the ProcessAnnotatedType event is not fired. > However, an extension A may register an AnnotatedType X via addAnnotatedType() and an extension B might want to react on the presence of AnnotatedType X. Therefore, it would be great to have the ProcessAnnotatedType fired also for AnnotatedTypes registered programatically in the BeforeBeanDiscovery phase. -- 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-30) An API for managing built in contexts

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-30?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-30: ------------------------- Fix Version/s: TBD > An API for managing built in contexts > ------------------------------------- > > Key: CDI-30 > URL: https://issues.jboss.org/browse/CDI-30 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Contexts > Affects Versions: 1.0 > Reporter: Nicklas Karlsson > Fix For: TBD > > > Add management API for built in contexts allowing them to be reused as needed. -- 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-71) Make it possible to obtain the qualifiers used when the currently observed event was fired

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-71?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-71: ------------------------- Fix Version/s: TBD > Make it possible to obtain the qualifiers used when the currently observed event was fired > ------------------------------------------------------------------------------------------ > > Key: CDI-71 > URL: https://issues.jboss.org/browse/CDI-71 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Events > 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-93) Support producers with a type variable bean type

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-93?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-93: ------------------------- Fix Version/s: TBD > Support producers with a type variable bean type > ------------------------------------------------ > > Key: CDI-93 > URL: https://issues.jboss.org/browse/CDI-93 > Project: CDI Specification Issues > Issue Type: Feature Request > 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-42) Allow you to inject the intercepted bean into an Interceptor

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-42?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-42: ------------------------- Fix Version/s: TBD > Allow you to inject the intercepted bean into an Interceptor > ------------------------------------------------------------ > > Key: CDI-42 > URL: https://issues.jboss.org/browse/CDI-42 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Interceptors > 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-21) Support PostConstruct callbacks in Extension class

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-21?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-21: ------------------------- Fix Version/s: TBD > Support PostConstruct callbacks in Extension class > -------------------------------------------------- > > Key: CDI-21 > URL: https://issues.jboss.org/browse/CDI-21 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Portable Extensions > Affects Versions: 1.0 > Reporter: Sivakumar Thyagarajan > Priority: Minor > Fix For: TBD > > > It is sometimes useful to get to know after a portable extension class has been instantiated, so that the state of the Extension could be initialized [ie not establishing state in the constructor and having it called twice when the Extension is proxied]. Though the 1.0 specification does not require this, it would be useful to support @PostConstruct callback on Extension class in the next version of the specification. > Please see https://jira.jboss.org/browse/WELD-713 for additional information on this issue. -- 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-86) Support firing general purpose lifecycle events in Java EE environments

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-86?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-86: ------------------------- Fix Version/s: TBD > Support firing general purpose lifecycle events in Java EE environments > ----------------------------------------------------------------------- > > Key: CDI-86 > URL: https://issues.jboss.org/browse/CDI-86 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration > 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-7) Section 10.2, bullet 3, first paragraph contradicts the rest of the section

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-7?page=com.atlassian.jira.plugin.syst... ] Pete Muir updated CDI-7: ------------------------ Fix Version/s: TBD (was: 1.1) > Section 10.2, bullet 3, first paragraph contradicts the rest of the section > --------------------------------------------------------------------------- > > Key: CDI-7 > URL: https://issues.jboss.org/browse/CDI-7 > Project: CDI Specification Issues > Issue Type: Task > Components: Events > Affects Versions: 1.0 > Reporter: Pete Muir > Priority: Blocker > Fix For: TBD > > > "The observer method has all the event qualifiers." > This contradicts the examples (section 10.2.3) and the use of @Any, all of which indicate that less specific observer methods are also invoked. -- 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-49) The availability of the BeanManager should follow the normal EE visibility rules

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-49?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-49: ------------------------- Fix Version/s: TBD > The availability of the BeanManager should follow the normal EE visibility rules > -------------------------------------------------------------------------------- > > Key: CDI-49 > URL: https://issues.jboss.org/browse/CDI-49 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration, Packaging and Deployment, Resolution > Affects Versions: 1.0 > Environment: JSR-000316 Java Platform, Enterprise Edition 6 Specification > Reporter: Aslak Knutsen > Fix For: TBD > > > EE 6 spec > EE.5.19 > A bean manager is only available in modules in which CDI has been enabled. > In e.g. a EAR deployment, a WAR module can see a EJB module. With CDI enabled in the EJB, the WAR can only see the BeanManager if the WAR itself is also CDI enabled. In cases where you want to do dynamic introspection of available beans etc, this is a bit cumbersome, especially since the introspecting code can be in a packaged jar inside a unknown WAR.. -- 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-44) Clarify that interceptors must be implemented using subclassing, and clarify the behaviour of self-invocation

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-44?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-44: ------------------------- Fix Version/s: TBD > Clarify that interceptors must be implemented using subclassing, and clarify the behaviour of self-invocation > ------------------------------------------------------------------------------------------------------------- > > Key: CDI-44 > URL: https://issues.jboss.org/browse/CDI-44 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Interceptors > Affects Versions: 1.0 > Reporter: Stuart Douglas > Fix For: TBD > > > When implementing interception using proxying the behaour of self invocation is quite well defined, if a method is invoked on the proxy it is intercepted, if it is invoked on the actual bean (usually through self-invocation) it is not. > When implementing interception though sub classing this is much less well definied, and the only way to track if an invocation is intercepted or not is through a thread local flag. At the moment in weld this is reset when a call is made on a client proxy, so if we have an intercepted bean A and a SessionScoped bean B and A invokes B when invokes A the second call to A is intercepted. If however B is pseudo scoped, then the second invocation is not intercepted. The correct behaviour here should be specified by the specification. -- 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 January 2011