February 2011 - cdi-dev - Jboss List Archives

[JBoss JIRA] Updated: (CDI-82) Clarify the usage of EJB3 interceptors as managed beans

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-82?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-82: ------------------------- Issue Type: Bug (was: Feature Request) Description: Background: http://lists.jboss.org/pipermail/weld-dev/2010-April/002484.html was: Background: http://lists.jboss.org/pipermail/weld-dev/2010-April/002484.html > Clarify the usage of EJB3 interceptors as managed beans > ------------------------------------------------------- > > Key: CDI-82 > URL: https://issues.jboss.org/browse/CDI-82 > Project: CDI Specification Issues > Issue Type: Bug > Components: Beans, Interceptors, Java EE integration > Affects Versions: 1.0 > Reporter: Marius Bogoevici > Fix For: TBD > > > Background: > http://lists.jboss.org/pipermail/weld-dev/2010-April/002484.html -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-46) Clarify in the specification that extensions do not require a beans.xml file

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-46?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-46: ------------------------- Issue Type: Bug (was: Feature Request) > Clarify in the specification that extensions do not require a beans.xml file > ---------------------------------------------------------------------------- > > Key: CDI-46 > URL: https://issues.jboss.org/browse/CDI-46 > Project: CDI Specification Issues > Issue Type: Bug > Components: Packaging and Deployment > Affects Versions: 1.0 > Reporter: Shane Bryzak > Fix For: TBD > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-56) Clarify that scope types should not have members

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-56?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-56: ------------------------- Issue Type: Bug (was: Feature Request) > Clarify that scope types should not have members > ------------------------------------------------ > > Key: CDI-56 > URL: https://issues.jboss.org/browse/CDI-56 > Project: CDI Specification Issues > Issue Type: Bug > Components: Concepts > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: TBD > > > The spec should mention that @NormalScope annotations should not have annotation members. Perhaps this should be a definition error. javax.inject.Scope already mentions this. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[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: ------------------------- Issue Type: Feature Request (was: Task) > 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: Feature Request > 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

14 years, 1 month

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: ------------------------- Issue Type: Bug (was: Feature Request) > 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: Bug > 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

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-6) Clarify InjectionTarget method parameters

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-6?page=com.atlassian.jira.plugin.syst... ] Pete Muir updated CDI-6: ------------------------ Issue Type: Bug (was: Task) > Clarify InjectionTarget method parameters > ----------------------------------------- > > Key: CDI-6 > URL: https://issues.jboss.org/browse/CDI-6 > Project: CDI Specification Issues > Issue Type: Bug > Components: Portable Extensions > Affects Versions: 1.0 > Reporter: Jozef Hartinger > Fix For: TBD > > > For the inject() method, the spec says: "inject() performs dependency injection upon the given object". It is not clear to me what does the "given object" refer two. if the CDI implementation uses proxies to implement interceptors and decorators, I can see two candidates for "the given object": > - the product of the produce() method including interceptors and decorators -> a proxy > - the target instance -> the object created by calling a constructor (no interception/decoration) > Arguments for the first option > - Let's have and extension that adds additional dependency injection capabilities by providing a custom InjectionTarget implementation and wrapping default InjectionTarget instances with custom ones. The custom InjectionTarget implementation does the additional DI in the inject() method and delegates to the default InjectionTarget instance to finish the injection. This implementation needs a direct access to the target instance (it cannot access field values through a proxy) > - Interceptor-like behavior - similarity to interceptors, where the InvocationContext.getTarget() returns the (non-intercepted) target instance > Arguments for the second option > - the contract of the produce() method says: "produce() calls the constructor annotated @Inject if it exists, or the constructor with no parameters otherwise, as defined in Section 5.5.1, "Injection using the bean constructor", and returns the resulting instance. If the class has inter- ceptors, produce() is responsible for building the interceptors and decorators of the instance." which means it returns an intercepted/decorated instance. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

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: ------------------------ Issue Type: Bug (was: Task) > 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: Bug > 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

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (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 updated CDI-23: ------------------------- Issue Type: Feature Request (was: Bug) > 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 > Fix For: TBD > > > 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

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-40) XSD missing enable element

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-40?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-40: ------------------------- Issue Type: Bug (was: Feature Request) > XSD missing enable element > -------------------------- > > Key: CDI-40 > URL: https://issues.jboss.org/browse/CDI-40 > Project: CDI Specification Issues > Issue Type: Bug > Components: Packaging and Deployment > Affects Versions: 1.0 > Reporter: Jason Porter > Assignee: Pete Muir > Fix For: TBD > > > Section 12.3 says there's an enable element, it's not there in the XSD. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-40) XSD missing enable element

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-40?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-40: ------------------------- Component/s: (was: Javadoc and API) > XSD missing enable element > -------------------------- > > Key: CDI-40 > URL: https://issues.jboss.org/browse/CDI-40 > Project: CDI Specification Issues > Issue Type: Bug > Components: Packaging and Deployment > Affects Versions: 1.0 > Reporter: Jason Porter > Assignee: Pete Muir > Fix For: TBD > > > Section 12.3 says there's an enable element, it's not there in the XSD. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev February 2011