May 2011 - cdi-dev - Jboss List Archives

[JBoss JIRA] Updated: (CDI-12) Specifically exclude methods inherited from java.lang.Object from the list of business method invocations

by Marius Bogoevici (JIRA)

[ https://issues.jboss.org/browse/CDI-12?page=com.atlassian.jira.plugin.sys... ] Marius Bogoevici updated CDI-12: -------------------------------- Fix Version/s: 1.1 (Confirmed) (was: 1.1 (Proposed)) > Specifically exclude methods inherited from java.lang.Object from the list of business method invocations > --------------------------------------------------------------------------------------------------------- > > Key: CDI-12 > URL: https://issues.jboss.org/browse/CDI-12 > Project: CDI Specification Issues > Issue Type: Bug > Components: Beans > Affects Versions: 1.0 > Reporter: Marius Bogoevici > Assignee: Marius Bogoevici > Priority: Optional > Fix For: 1.1 (Confirmed) > > > Without this specific exclusion, there is a theoretical possibility to treat these methods as business method invocations. > - they are defined on the object; > - will be present on the contextual reference; -- 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] Resolved: (CDI-12) Specifically exclude methods inherited from java.lang.Object from the list of business method invocations

by Marius Bogoevici (JIRA)

[ https://issues.jboss.org/browse/CDI-12?page=com.atlassian.jira.plugin.sys... ] Marius Bogoevici resolved CDI-12. --------------------------------- Resolution: Done > Specifically exclude methods inherited from java.lang.Object from the list of business method invocations > --------------------------------------------------------------------------------------------------------- > > Key: CDI-12 > URL: https://issues.jboss.org/browse/CDI-12 > Project: CDI Specification Issues > Issue Type: Bug > Components: Beans > Affects Versions: 1.0 > Reporter: Marius Bogoevici > Assignee: Marius Bogoevici > Priority: Optional > Fix For: 1.1 (Confirmed) > > > Without this specific exclusion, there is a theoretical possibility to treat these methods as business method invocations. > - they are defined on the object; > - will be present on the contextual reference; -- 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] Resolved: (CDI-28) Abstract methods on decorators

by Marius Bogoevici (JIRA)

[ https://issues.jboss.org/browse/CDI-28?page=com.atlassian.jira.plugin.sys... ] Marius Bogoevici resolved CDI-28. --------------------------------- Resolution: Done https://github.com/jboss/cdi/pull/26 > Abstract methods on decorators > ------------------------------ > > Key: CDI-28 > URL: https://issues.jboss.org/browse/CDI-28 > Project: CDI Specification Issues > Issue Type: Bug > Components: Decorators > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Marius Bogoevici > Fix For: 1.1 (Proposed) > > > If a method is abstract: > * if it is a method of a decorated type, it has a generated implementation that calls the delegate > * otherwise, definition error -- 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-28) Abstract methods on decorators

by Marius Bogoevici (JIRA)

[ https://issues.jboss.org/browse/CDI-28?page=com.atlassian.jira.plugin.sys... ] Marius Bogoevici updated CDI-28: -------------------------------- Fix Version/s: 1.1 (Confirmed) (was: 1.1 (Proposed)) > Abstract methods on decorators > ------------------------------ > > Key: CDI-28 > URL: https://issues.jboss.org/browse/CDI-28 > Project: CDI Specification Issues > Issue Type: Bug > Components: Decorators > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Marius Bogoevici > Fix For: 1.1 (Confirmed) > > > If a method is abstract: > * if it is a method of a decorated type, it has a generated implementation that calls the delegate > * otherwise, definition error -- 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] Resolved: (CDI-41) Improve clarity of decorators

by Marius Bogoevici (JIRA)

[ https://issues.jboss.org/browse/CDI-41?page=com.atlassian.jira.plugin.sys... ] Marius Bogoevici resolved CDI-41. --------------------------------- Resolution: Done Pull request here: https://github.com/jboss/cdi/pull/25 > Improve clarity of decorators > ----------------------------- > > Key: CDI-41 > URL: https://issues.jboss.org/browse/CDI-41 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Decorators > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Marius Bogoevici > Fix For: 1.1 (Confirmed) > > > Remove bullet points from > "The decorator intercepts every method: > > • declared by a decorated type of the decorator > > • that is implemented by the bean class of the decorator." > they are removing clarity from the spec -- 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-41) Improve clarity of decorators

by Marius Bogoevici (JIRA)

[ https://issues.jboss.org/browse/CDI-41?page=com.atlassian.jira.plugin.sys... ] Marius Bogoevici updated CDI-41: -------------------------------- Fix Version/s: 1.1 (Confirmed) (was: 1.1 (Proposed)) > Improve clarity of decorators > ----------------------------- > > Key: CDI-41 > URL: https://issues.jboss.org/browse/CDI-41 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Decorators > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Marius Bogoevici > Fix For: 1.1 (Confirmed) > > > Remove bullet points from > "The decorator intercepts every method: > > • declared by a decorated type of the decorator > > • that is implemented by the bean class of the decorator." > they are removing clarity from the spec -- 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] Issue Comment Edited: (CDI-6) Clarify InjectionTarget method parameters

by Marius Bogoevici (JIRA)

[ https://issues.jboss.org/browse/CDI-6?page=com.atlassian.jira.plugin.syst... ] Marius Bogoevici edited comment on CDI-6 at 5/24/11 6:08 PM: ------------------------------------------------------------- Proposed: "inject() performs dependency injection upon the instance returned by the invocation of the produce() method" was (Author: marius.bogoevici): Proposed: "inject() performs dependency injection upon the value returned by the invocation of the produce() method" > Clarify InjectionTarget method parameters > ----------------------------------------- > > Key: CDI-6 > URL: https://issues.jboss.org/browse/CDI-6 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Portable Extensions > Affects Versions: 1.0 > Reporter: Jozef Hartinger > Assignee: Marius Bogoevici > Priority: Minor > Fix For: 1.1 (Proposed) > > > 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

13 years, 3 months

1
0
0 / 0

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

by Marius Bogoevici (JIRA)

[ https://issues.jboss.org/browse/CDI-6?page=com.atlassian.jira.plugin.syst... ] Marius Bogoevici commented on CDI-6: ------------------------------------ Proposed: "inject() performs dependency injection upon the value returned by the invocation of the produce() method" > Clarify InjectionTarget method parameters > ----------------------------------------- > > Key: CDI-6 > URL: https://issues.jboss.org/browse/CDI-6 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Portable Extensions > Affects Versions: 1.0 > Reporter: Jozef Hartinger > Assignee: Marius Bogoevici > Priority: Minor > Fix For: 1.1 (Proposed) > > > 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

13 years, 3 months

1
0
0 / 0

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

by Marius Bogoevici (JIRA)

[ https://issues.jboss.org/browse/CDI-82?page=com.atlassian.jira.plugin.sys... ] Marius Bogoevici edited comment on CDI-82 at 5/24/11 6:00 PM: -------------------------------------------------------------- Proposed fix: if a class is declared in the @Interceptors clause of a managed bean, it will be treated automatically as if it were annotated with @Interceptor. was (Author: marius.bogoevici): Proposed fix: if a class is declared in the @Interceptors clause of a managed bean, it is automatically vetoed from the deployment. > 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: Clarification > Components: Beans, Interceptors, Java EE integration > Affects Versions: 1.0 > Reporter: Marius Bogoevici > Assignee: Marius Bogoevici > Fix For: 1.1 (Proposed) > > > 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

13 years, 3 months

1
0
0 / 0

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

by Marius Bogoevici (JIRA)

[ https://issues.jboss.org/browse/CDI-82?page=com.atlassian.jira.plugin.sys... ] Marius Bogoevici commented on CDI-82: ------------------------------------- Proposed fix: if a class is declared in the @Interceptors clause of a managed bean, it is automatically vetoed from the deployment. > 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: Clarification > Components: Beans, Interceptors, Java EE integration > Affects Versions: 1.0 > Reporter: Marius Bogoevici > Assignee: Marius Bogoevici > Fix For: 1.1 (Proposed) > > > 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

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 May 2011