May 2017 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-703) Carify indirect specialization

by Mark Struberg (JIRA)

[ https://issues.jboss.org/browse/CDI-703?page=com.atlassian.jira.plugin.sy... ] Mark Struberg commented on CDI-703: ----------------------------------- [~manovotn] CDI-441 makes clear that the rules don't only apply to X extends Z extends Y but also X extends Z2 extends Z1 extends Y situations. But it does not even mention Qualifiers... > Carify indirect specialization > ------------------------------ > > Key: CDI-703 > URL: https://issues.jboss.org/browse/CDI-703 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Inheritance and Specialization > Affects Versions: 2.0 .Final > Reporter: Antoine Sabot-Durand > > Indirect specialization in chapter 4.3.1 lacks clarification regarding intermediate beans attributes (qualifier and name) on specializing bean bean. > Discussion in CDITCK-580 illustrates this concern. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

Clarification - how does addPackages work?

by John Ament

While porting the CDI spec to the geronimo project, I noticed that SeContainerInitializer#addPackages (without the boolean) doesn't specify whether its recursive or not. I believe its not recursive but wanted to confirm this. E.g. the behavior is the same as calling addPackages(false, Package....) John ________________________________ NOTICE: This e-mail message and any attachments may contain confidential, proprietary, and/or privileged information which should be treated accordingly. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this message, and destroy all physical and electronic copies. Thank you.

7 years, 7 months

3
6
0 / 0

[JBoss JIRA] (CDI-704) Clarify that SeContainerInitializer.addPackages is by default not recursive

by John Ament (JIRA)

John Ament created CDI-704: ------------------------------ Summary: Clarify that SeContainerInitializer.addPackages is by default not recursive Key: CDI-704 URL: https://issues.jboss.org/browse/CDI-704 Project: CDI Specification Issues Issue Type: Clarification Reporter: John Ament Neither the spec nor the javadocs make it clear that this method is by default not recursive, the equivalent of calling addPackages(false, ...) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-78) Clarify how isDelegate() behaves on InjectionPoint, and what happens when an InjectionPoint is injected into a Decorator

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-78?page=com.atlassian.jira.plugin.sys... ] Antoine Sabot-Durand updated CDI-78: ------------------------------------ Fix Version/s: 2.1 (Discussion) > Clarify how isDelegate() behaves on InjectionPoint, and what happens when an InjectionPoint is injected into a Decorator > ------------------------------------------------------------------------------------------------------------------------ > > Key: CDI-78 > URL: https://issues.jboss.org/browse/CDI-78 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Decorators > Affects Versions: 1.0 > Reporter: Pete Muir > Labels: F2F2016 > Fix For: 2.1 (Discussion) > > > The InjectionPoint should be that of the injection into the consumer, and isDelegate() should return false. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-78) Clarify how isDelegate() behaves on InjectionPoint, and what happens when an InjectionPoint is injected into a Decorator

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-78?page=com.atlassian.jira.plugin.sys... ] Antoine Sabot-Durand edited comment on CDI-78 at 5/30/17 4:20 AM: ------------------------------------------------------------------ 2 scenarios here. h2. InjectionPoint relates to the decorator bean itself As a decorator can't be injected directly since it's not available for injection as stated in 5.1.4, so {{InjectionPoint}} of a decorator should always return null. h2. InjectionPoint relates to the decorated bean It could be nice to have information about {{InjectionPoint}} of the decorated bean in the decorator, but it can be confusing to deal with it: decorator can decorate dependent and non-dependent beans at the same time. So, if we don't want to break the spec, we should forbid it if at least one decorated bean is not dependent. h2. My proposal {{InjectionPoint}} with @Default qualifier injected in decorator (or interceptor BTW), should be considered as scenario 1 and always return null. To support injection of decorated bean's {{InjectionPoint}} we should use the {{@Decorated}} qualifier ({{@Inject @Decorated InjectionPoint}}) allowing to have the IP instance if decorated bean is dependent or null if it is not. It won't violate the spec and be less confusing for users (we can assume that a user adding such a qualifier probably knows what he's doing). Again this proposal is also interesting for Interceptors. WDYT ? was (Author: antoinesabot-durand): 2 scenarios here. h2. InjectionPoint relates to the decorator bean itself As a decorator can't be injected directly since it's not available for injection as stated in 5.1.4, so {{InjectionPoint}} of a decorator should always return null. h2. InjectionPoint relates to the decorated bean It could be nice to have information about {{InjectionPoint}} of the decorated bean in the decorator, but it can be confusing to deal with it: decorator can decorate dependent and non-dependent beans at the same time. So, if we don't want to break the spec, we should forbid it if at leat one decorated bean is not dependent. h2. My proposal {{InjectionPoint}} with @Default qualifier injected in decorator (or interceptor BTW), should be considered as scenario 1 and always return null. To support injection of decorated bean's {{InjectionPoint}} we should use the {{@Decorated}} qualifier ({{@Inject @Decorated InjectionPoint}}) allowing to have the IP instance if decorated bean is dependent or null if it is not. It won't violate the spec and be less confusing for users (we can assume that a user adding such a qualifier probably knows what he's doing). Again this proposal is also interesting for Interceptors. WDYT ? > Clarify how isDelegate() behaves on InjectionPoint, and what happens when an InjectionPoint is injected into a Decorator > ------------------------------------------------------------------------------------------------------------------------ > > Key: CDI-78 > URL: https://issues.jboss.org/browse/CDI-78 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Decorators > Affects Versions: 1.0 > Reporter: Pete Muir > Labels: F2F2016 > > The InjectionPoint should be that of the injection into the consumer, and isDelegate() should return false. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-78) Clarify how isDelegate() behaves on InjectionPoint, and what happens when an InjectionPoint is injected into a Decorator

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-78?page=com.atlassian.jira.plugin.sys... ] Antoine Sabot-Durand commented on CDI-78: ----------------------------------------- 2 scenarios here. h2. InjectionPoint relates to the decorator bean itself As a decorator can't be injected directly since it's not available for injection as stated in 5.1.4, so {{InjectionPoint}} of a decorator should always return null. h2. InjectionPoint relates to the decorated bean It could be nice to have information about {{InjectionPoint}} of the decorated bean in the decorator, but it can be confusing to deal with it: decorator can decorate dependent and non-dependent beans at the same time. So, if we don't want to break the spec, we should forbid it if at leat one decorated bean is not dependent. h2. My proposal {{InjectionPoint}} with @Default qualifier injected in decorator (or interceptor BTW), should be considered as scenario 1 and always return null. To support injection of decorated bean's {{InjectionPoint}} we should use the {{@Decorated}} qualifier ({{@Inject @Decorated InjectionPoint}}) allowing to have the IP instance if decorated bean is dependent or null if it is not. It won't violate the spec and be less confusing for users (we can assume that a user adding such a qualifier probably knows what he's doing). Again this proposal is also interesting for Interceptors. WDYT ? > Clarify how isDelegate() behaves on InjectionPoint, and what happens when an InjectionPoint is injected into a Decorator > ------------------------------------------------------------------------------------------------------------------------ > > Key: CDI-78 > URL: https://issues.jboss.org/browse/CDI-78 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Decorators > Affects Versions: 1.0 > Reporter: Pete Muir > Labels: F2F2016 > > The InjectionPoint should be that of the injection into the consumer, and isDelegate() should return false. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-703) Carify indirect specialization

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/CDI-703?page=com.atlassian.jira.plugin.sy... ] Matej Novotny commented on CDI-703: ----------------------------------- What part exactly would you like to clarify? As a part of CDI-441 (2.0) we enhanced the wording making it clear that the relation is *transitive*. And that, in my opinion, should have quite clear implications in this regard. > Carify indirect specialization > ------------------------------ > > Key: CDI-703 > URL: https://issues.jboss.org/browse/CDI-703 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Inheritance and Specialization > Affects Versions: 2.0 .Final > Reporter: Antoine Sabot-Durand > > Indirect specialization in chapter 4.3.1 lacks clarification regarding intermediate beans attributes (qualifier and name) on specializing bean bean. > Discussion in CDITCK-580 illustrates this concern. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-703) Carify indirect specialization

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-703?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-703: ------------------------------------- Description: Indirect specialization in chapter 4.3.1 lacks clarification regarding intermediate beans attributes (qualifier and name) on specializing bean bean. Discussion in CDITCK-580 illustrates this concern. was: Indirect specialization in chapter 4.3.1 lacks clarification regarding intermediate beans attributes (qualifier) and final bean. Discussion in CDITCK-580 illustrates this concern. > Carify indirect specialization > ------------------------------ > > Key: CDI-703 > URL: https://issues.jboss.org/browse/CDI-703 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Inheritance and Specialization > Affects Versions: 2.0 .Final > Reporter: Antoine Sabot-Durand > > Indirect specialization in chapter 4.3.1 lacks clarification regarding intermediate beans attributes (qualifier and name) on specializing bean bean. > Discussion in CDITCK-580 illustrates this concern. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-703) Carify indirect specialization

by Antoine Sabot-Durand (JIRA)

Antoine Sabot-Durand created CDI-703: ---------------------------------------- Summary: Carify indirect specialization Key: CDI-703 URL: https://issues.jboss.org/browse/CDI-703 Project: CDI Specification Issues Issue Type: Clarification Components: Inheritance and Specialization Affects Versions: 2.0 .Final Reporter: Antoine Sabot-Durand Indirect specialization in chapter 4.3.1 lacks clarification regarding intermediate beans attributes (qualifier) and final bean. Discussion in CDITCK-580 illustrates this concern. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-78) Clarify how isDelegate() behaves on InjectionPoint, and what happens when an InjectionPoint is injected into a Decorator

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/CDI-78?page=com.atlassian.jira.plugin.sys... ] Tomas Remes reopened CDI-78: ---------------------------- Assignee: (was: Pete Muir) See my previous comment. > Clarify how isDelegate() behaves on InjectionPoint, and what happens when an InjectionPoint is injected into a Decorator > ------------------------------------------------------------------------------------------------------------------------ > > Key: CDI-78 > URL: https://issues.jboss.org/browse/CDI-78 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Decorators > Affects Versions: 1.0 > Reporter: Pete Muir > Labels: F2F2016 > > The InjectionPoint should be that of the injection into the consumer, and isDelegate() should return false. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev May 2017