November 2013 - cdi-dev - Jboss List Archives

Invitation: CDI 1.1 EG meeting - lun. 18 nov. 2013 18:00 - 19:00 (Perso)

by Antoine Sabot-Durand

Vous avez été invité à l'événement suivant. Titre : CDI 1.1 EG meeting Discussing about CDI 1.1.1 MR scope The Google Hangout link for the meeting is https://plus.google.com/hangouts/_/calendar/YW50b2luZS5zYWJvdGR1cmFuZEBnb... Date : lun. 18 nov. 2013 18:00 – 19:00 Paris Appel vidéo: Participer à un appel vidéo <https://plus.google.com/hangouts/_/calendar/YW50b2luZS5zYWJvdGR1cmFuZEBnb...> Agenda : Perso Participants : * Antoine Sabot-Durand- organisateur * cdi-dev(a)lists.jboss.org Détails de l'événement : https://www.google.com/calendar/event?action=VIEW&eid=XzY1MTQyY2hwNmtyMzh... Invitation de Google Agenda : https://www.google.com/calendar/ Vous recevez ce message à l'adresse cdi-dev(a)lists.jboss.org, car vous participez à cet événement. Pour ne plus recevoir de notifications pour cet événement à l'avenir, refusez cet événement. Vous avez également la possibilité de créer un compte Google sur la page https://www.google.com/calendar/ et de définir vous-même les paramètres de notification pour l'intégralité de votre agenda.

11 years, 1 month

1
0
0 / 0

CDI EG Hangout, Monday 18th GMT

by Antoine Sabot-Durand

Hi all, I propose we organize our Hangout next monday at 18:00 GMT [1] The agenda will focus on CDI 1.1.1 scope. To ease my life, it would be great that each EG member follow the CDI Spec Google+ page [2], so I can send invitation easily Thanks [1] http://www.timeanddate.com/worldclock/fixedtime.html?msg=CDI+EG+Hangout&i... [2] https://plus.google.com/111798907065326961264 Antoine

11 years, 1 month

2
2
0 / 0

[JBoss JIRA] (CDI-77) Clarify what happens when the user creates a unbound recursive injection with Dependent scoped beans

by Arne Limburg (JIRA)

[ https://issues.jboss.org/browse/CDI-77?page=com.atlassian.jira.plugin.sys... ] Arne Limburg commented on CDI-77: --------------------------------- Hmm, but why (but of a technical point of view) should the spec differentiate between normal scoped beans and dependent beans? Either we feel that circular injection is not a good way to design applications and want to forbit it in either situation or we allow it and maybe document behavior where it simply does not work. By the way, how does the spec treat situations where a dependent bean has an interceptor-binding or decorator and is not proxiable? > Clarify what happens when the user creates a unbound recursive injection with Dependent scoped beans > ---------------------------------------------------------------------------------------------------- > > Key: CDI-77 > URL: https://issues.jboss.org/browse/CDI-77 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Resolution > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: TBD > > > for example > class Foo { > @Inject Bar bar; > } > class bar { > @Inject Foo foo; > } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (CDI-77) Clarify what happens when the user creates a unbound recursive injection with Dependent scoped beans

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-77?page=com.atlassian.jira.plugin.sys... ] Antoine Sabot-Durand commented on CDI-77: ----------------------------------------- [~arnelim] I agree with [~rmannibucau]. I think we should avoid usage of proxies on dependent bean (at least limit them to he strict necessary). IMO the spec shouldn't be driven by what's possible but by what's makes sense or is a good practice. Circular injection doesn't feel a good way to design application to me. Now perhaps you can give us an example in which it would be useful ? > Clarify what happens when the user creates a unbound recursive injection with Dependent scoped beans > ---------------------------------------------------------------------------------------------------- > > Key: CDI-77 > URL: https://issues.jboss.org/browse/CDI-77 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Resolution > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: TBD > > > for example > class Foo { > @Inject Bar bar; > } > class bar { > @Inject Foo foo; > } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (CDI-77) Clarify what happens when the user creates a unbound recursive injection with Dependent scoped beans

by Romain Manni-Bucau (JIRA)

[ https://issues.jboss.org/browse/CDI-77?page=com.atlassian.jira.plugin.sys... ] Romain Manni-Bucau commented on CDI-77: --------------------------------------- It is important to not have proxies for simple @Dependent beans (some can be not proxiable). So the issue is real but honestly not a real life issue IMO. you quickly understand your issue when you encounter it and thats a "standard" design issue. > Clarify what happens when the user creates a unbound recursive injection with Dependent scoped beans > ---------------------------------------------------------------------------------------------------- > > Key: CDI-77 > URL: https://issues.jboss.org/browse/CDI-77 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Resolution > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: TBD > > > for example > class Foo { > @Inject Bar bar; > } > class bar { > @Inject Foo foo; > } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

Leveraging CDI adoption

by Antoine Sabot-Durand

Hi, You may have remarked that I have rebooted Twitter account renaming from @jsr346 to @cdispec. I also launched a G+ page [1]. Beyond using these account to post news about the spec, I propose that we use these to post all news related to CDI : implementation release, article, dedicated (Deltaspike) or supporting framework, and talk about them. The idea is to give CDI more visibility and leverage its adoption and building a real community behind the spec. Your feedback or opinion on the subject is most welcome. [1] https://plus.google.com/b/111798907065326961264/111798907065326961264 Antoine

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (CDI-77) Clarify what happens when the user creates a unbound recursive injection with Dependent scoped beans

by Arne Limburg (JIRA)

[ https://issues.jboss.org/browse/CDI-77?page=com.atlassian.jira.plugin.sys... ] Arne Limburg commented on CDI-77: --------------------------------- Hmm, if we don't talk about constructor injection, this is not a problem at all. So I don't think, we should forbid this. And for constructor injection we could create a proxy. We already create proxies for Dependent beans (i.e. when they have interceptor bindings). So why should we not create a proxy in this situation? > Clarify what happens when the user creates a unbound recursive injection with Dependent scoped beans > ---------------------------------------------------------------------------------------------------- > > Key: CDI-77 > URL: https://issues.jboss.org/browse/CDI-77 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Resolution > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: TBD > > > for example > class Foo { > @Inject Bar bar; > } > class bar { > @Inject Foo foo; > } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (CDI-323) Specify what happens when a bean, that has an injection point of type InjectionPoint, is created via BeanManager#getReference(...)

by Arne Limburg (JIRA)

[ https://issues.jboss.org/browse/CDI-323?page=com.atlassian.jira.plugin.sy... ] Arne Limburg commented on CDI-323: ---------------------------------- Yes, 6.5.3 sounds fine. Maybe we should add an example for the latter case like "a null value if it is not being injected into any injection point, i.e. it is received via BeanManager#getReference"? > Specify what happens when a bean, that has an injection point of type InjectionPoint, is created via BeanManager#getReference(...) > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: CDI-323 > URL: https://issues.jboss.org/browse/CDI-323 > Project: CDI Specification Issues > Issue Type: Clarification > Affects Versions: 1.1.PRD > Reporter: Arne Limburg > > The same problem applys to events that are fired via BeanManager#fireEvent when an observer exists, that has an InjectionPoint parameter -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (CDI-403) why decorator requires interface

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-403?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand commented on CDI-403: ------------------------------------------ Interesting point, but a probably too big for a CDI 1.1 MR. > why decorator requires interface > -------------------------------- > > Key: CDI-403 > URL: https://issues.jboss.org/browse/CDI-403 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Mathieu Lachance > > As discussed with Jozef Hartinger on the WELD forum thread (see forum reference and CDI-224), > would it be possible to revisit why decorator requires an interface ? > I do not understand the semantic difference between: > 1. a decorator to be an abstract class which implements an interface, which delegate to the same interface. > 2. a decorator to be a concrete class which extends a another class, which delegates to the same class. > Why 1. should be allowed and why 2. should be disallowed ? > As stated in CDI-224, if there is no technical reason of disallowing 2., should it be then considerate as a vendor specific feature to support it whether or not ? > It is kind of sad that only decorators requires an interface while all the others Java EE 6 features do not. > Thanks, -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (CDI-323) Specify what happens when a bean, that has an injection point of type InjectionPoint, is created via BeanManager#getReference(...)

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-323?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand commented on CDI-323: ------------------------------------------ Isn't it treated by 6.5.3? {quote} The container must ensure that every injection point of type InjectionPoint and qualifier @Default of any dependent object instantiated during this process receives: * an instance of InjectionPoint representing the injection point into which the dependent object will be injected, or * a null value if it is not being injected into any injection point. {quote} > Specify what happens when a bean, that has an injection point of type InjectionPoint, is created via BeanManager#getReference(...) > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: CDI-323 > URL: https://issues.jboss.org/browse/CDI-323 > Project: CDI Specification Issues > Issue Type: Clarification > Affects Versions: 1.1.PRD > Reporter: Arne Limburg > > The same problem applys to events that are fired via BeanManager#fireEvent when an observer exists, that has an InjectionPoint parameter -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev November 2013