November 2013 - cdi-dev - Jboss List Archives

by Antoine Sabot-Durand

Hi all, To be as efficient as possible I propose the following agenda for the meeting 1) MR proposed roadmap 2) Content of the proposed list 3) Try to have a 1st decision on big tickets (tickets with great impact on implementation or spec) - CDI-377 : automatic JSR-330 annotation processing problematic - CDI-370 : Expand @RequestScoped and @SessionScoped to account for WebSocket - others I’d like to avoid a 2 hours meeting, so let’s not talk about all ticket. We could choose to take 2 or 3 other big tickets for the next meeting. In the meanwhile discussion can continue on JIRA and ML For those who missed it the meeting hangout link is : https://plus.google.com/hangouts/_/calendar/YW50b2luZS5zYWJvdGR1cmFuZEBnb... Antoine

11 years, 1 month

3
4
0 / 0

CDi 1.1.1 MR

by Antoine Sabot-Durand

Hi all Maintenance Release is indeed quite critical. As stated by Pete we should have a tight scope but address significant issue or needed clarification. Some interoperability issues should also IMO be studied to see if we can address them in 1.1.1 (the https://issues.jboss.org/browse/CDI-377 comes to my mind). As we are a bit late on this MR, I propose to try to have it time boxed (deliver early, deliver often) to show we’re still alive ;) . My main idea is to prioritize issues, give us a deadline (not too straight) and do the maximum in this time frame. WDYT Antoine

11 years, 1 month

2
7
0 / 0

[JBoss JIRA] (CDI-406) Make stereotypes bean defining annotations

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-406?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-406: ------------------------------------- Labels: (was: cdi) > Make stereotypes bean defining annotations > ------------------------------------------ > > Key: CDI-406 > URL: https://issues.jboss.org/browse/CDI-406 > Project: CDI Specification Issues > Issue Type: Feature Request > Affects Versions: 1.1.FD > Reporter: Jozef Hartinger > Fix For: 1.1.1 (Proposed) > > > For example @Model -- 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-406) Make stereotypes bean defining annotations

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-406?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-406: ------------------------------------- Labels: cdi (was: ) > Make stereotypes bean defining annotations > ------------------------------------------ > > Key: CDI-406 > URL: https://issues.jboss.org/browse/CDI-406 > Project: CDI Specification Issues > Issue Type: Feature Request > Affects Versions: 1.1.FD > Reporter: Jozef Hartinger > Labels: cdi > Fix For: 1.1.1 (Proposed) > > > For example @Model -- 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

Having an official CDI tutorial and user forum

by Antoine Sabot-Durand

Hi all, First excuse my french in previous meeting invites. Obviously Google can speak english to you and keep sending french invitation ;). I launch this thread in reaction to the FUD or inaccuracies about CDI one can find on the web like this post [1]). As the spec is quite long to read and very theoretic, I think it would be useful to provide an official CDI 1.1 tutorial on cdi-spec site. It could allows us to be sure that people have an official overview of the spec and could be enhanced with use cases we would encounter on the web (stack overflow or other). I have the feeling such content is already nearly written by people in this ML, so if you have written introduction tutorial to CDI and agree to be reused on official site it would be great and time saving for me. In the same idea of community federation, I think it could be useful to launch a forum (Google group or other) to allow people to ask informal question about CDI and its eco system. People starting using CDI or casual users won’t use this mailing list and all of them think to use site like Stack Overflow. It would also a good mean to enhance our FAQ. What do you think ? Antoine [1] http://blog.frankel.ch/my-case-against-autowiring

11 years, 1 month

4
4
0 / 0

[JBoss JIRA] (CDI-407) Specifiy @Named @Alternatives

by Thomas Andraschko (JIRA)

[ https://issues.jboss.org/browse/CDI-407?page=com.atlassian.jira.plugin.sy... ] Thomas Andraschko updated CDI-407: ---------------------------------- Environment: (was: It's actually a must-have for product development and a common case. We would like to have multiple implementations in our core and just activate them via alternative. I talked with struberg and its currently not defined in the specs. e.g. @Named public class A @Named @Alternative public class B extends A What should acutally happen if B is activated via beans.xml? IMO B should be available in EL via "a" and "b".) Description: It's actually a must-have for product development and a common case. We would like to have multiple implementations in our core and just activate them via alternative. I talked with struberg and its currently not defined in the specs. e.g. @Named public class A @Named @Alternative public class B extends A What should acutally happen if B is activated via beans.xml? IMO B should be available in EL via "a" and "b". > Specifiy @Named @Alternatives > ----------------------------- > > Key: CDI-407 > URL: https://issues.jboss.org/browse/CDI-407 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Beans, Inheritance and Specialization > Reporter: Thomas Andraschko > > It's actually a must-have for product development and a common case. > We would like to have multiple implementations in our core and just activate them via alternative. > I talked with struberg and its currently not defined in the specs. > e.g. > @Named public class A > @Named @Alternative public class B extends A > What should acutally happen if B is activated via beans.xml? > IMO B should be available in EL via "a" and "b". -- 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-407) Specifiy @Named @Alternatives

by Thomas Andraschko (JIRA)

Thomas Andraschko created CDI-407: ------------------------------------- Summary: Specifiy @Named @Alternatives Key: CDI-407 URL: https://issues.jboss.org/browse/CDI-407 Project: CDI Specification Issues Issue Type: Clarification Components: Beans, Inheritance and Specialization Environment: It's actually a must-have for product development and a common case. We would like to have multiple implementations in our core and just activate them via alternative. I talked with struberg and its currently not defined in the specs. e.g. @Named public class A @Named @Alternative public class B extends A What should acutally happen if B is activated via beans.xml? IMO B should be available in EL via "a" and "b". Reporter: Thomas Andraschko -- 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-276) Clarify that scope annotations shouldn't be used at injection points

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-276?page=com.atlassian.jira.plugin.sy... ] Pete Muir commented on CDI-276: ------------------------------- Java EE specifications rarely contain as many error conditions as CDI, nor do they specify what happens in these situations as much as CDI does. So we could discuss with the EG introducing this warning requirement, but it's diverging a lot from other specs. Also, it would be very hard to test that it actually happens AFAICT. > Clarify that scope annotations shouldn't be used at injection points > -------------------------------------------------------------------- > > Key: CDI-276 > URL: https://issues.jboss.org/browse/CDI-276 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Contexts > Reporter: Nicklas Karlsson > Fix For: TBD > > > Sometimes you see people trying to do > @Inject @ApplicationScoped > private SomeRequestScopedBean sRSB; > It should be clarified that this has no effect. Could even throw a validation exception at deployment. -- 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

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

by antoine.sabotdurand＠gmail.com

Cet événement a été modifié. 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... Affichez votre événement sur la page http://www.google.com/calendar/event?action=VIEW&eid=XzY1MTQyY2hwNmtyMzhi.... Affichez votre événement sur la page http://www.google.com/calendar/event?action=VIEW&eid=XzY1MTQyY2hwNmtyMzhi.... (modifié) 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

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

by antoine.sabotdurand＠gmail.com

Cet événement a été modifié. 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... Affichez votre événement sur la page http://www.google.com/calendar/event?action=VIEW&eid=XzY1MTQyY2hwNmtyMzhi.... (modifié) 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev November 2013