July 2012 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-102) Support Injection of Servlet Contexts

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/CDI-102?page=com.atlassian.jira.plugin.sy... ] Lincoln Baxter III commented on CDI-102: ---------------------------------------- Yes, let's reopen this. We're running into it in JBoss Forge, of all places, which is not even related to Servlets aside from the fact that pulling in Weld forces us to deal with these scenarios. > Support Injection of Servlet Contexts > ------------------------------------- > > Key: CDI-102 > URL: https://issues.jboss.org/browse/CDI-102 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Priority: Minor > Fix For: 1.1.EDR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-50) Ability to veto beans, both unconditionally and based on classes visible

by Romain Manni-Bucau (JIRA)

[ https://issues.jboss.org/browse/CDI-50?page=com.atlassian.jira.plugin.sys... ] Romain Manni-Bucau commented on CDI-50: --------------------------------------- +1 IMO it is simply a packaging issue. > Ability to veto beans, both unconditionally and based on classes visible > ------------------------------------------------------------------------ > > Key: CDI-50 > URL: https://issues.jboss.org/browse/CDI-50 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Concepts, Packaging and Deployment > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1.EDR2 > > > This should support both a straight veto, and conditional based on classes available. > Seam Solder supports this as @Veto and @Requires({Foo.class, Bar.class}). > Mark Struberg proposed using @Optional -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-58) Clarify that there can be multiple AnnotatedType instances per Java class

by Mark Struberg (JIRA)

[ https://issues.jboss.org/browse/CDI-58?page=com.atlassian.jira.plugin.sys... ] Mark Struberg updated CDI-58: ----------------------------- Priority: Critical (was: Major) Description: This decision is really important to make. Either we remove/redefine BeanManager#getAnnoatadType(Class) or we remove the 'artificial annotated types'. Forum Reference: http://www.seamframework.org/Weld/PortableExtensionWishlist#H-ClarifyThat... (was: http://www.seamframework.org/Weld/PortableExtensionWishlist#H-ClarifyThat...) > Clarify that there can be multiple AnnotatedType instances per Java class > ------------------------------------------------------------------------- > > Key: CDI-58 > URL: https://issues.jboss.org/browse/CDI-58 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Beans, Portable Extensions > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Priority: Critical > Fix For: 1.1.EDR2 > > > This decision is really important to make. Either we remove/redefine BeanManager#getAnnoatadType(Class) or we remove the 'artificial annotated types'. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-3) Add add an event that fires after all ProcessAnnotatedType events that allows you to add new AnnotatedTypes

by Mark Struberg (JIRA)

[ https://issues.jboss.org/browse/CDI-3?page=com.atlassian.jira.plugin.syst... ] Mark Struberg commented on CDI-3: --------------------------------- see my comment in CDI-58. All this is depending on our understanding of AnnotatedType: Is there 1 per Class or do we allow 'artificial' AnnotatedTypes? > Add add an event that fires after all ProcessAnnotatedType events that allows you to add new AnnotatedTypes > ------------------------------------------------------------------------------------------------------------ > > Key: CDI-3 > URL: https://issues.jboss.org/browse/CDI-3 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Portable Extensions > Affects Versions: 1.0 > Reporter: Stuart Douglas > Fix For: 1.1 (Proposed) > > > At the moment AnnotatedTypes can only be added in the BeforeBeanDiscovery phase. This means that if you want to install additional beans based on the beans processed in the ProcessAnnotatedType phase you must instead add implementations of the Bean interface in the AfterBeanDiscovery phase. This interface is more limited than annotated type, and does not let you exactly mimic the behaviour of beans added as AnnotatedTypes. > Some of the things that the bean interface will not let you mimic are: > - Interceptors > - Disposal methods > - Producer fields for normal scoped beans -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-50) Ability to veto beans, both unconditionally and based on classes visible

by Mark Struberg (JIRA)

[ https://issues.jboss.org/browse/CDI-50?page=com.atlassian.jira.plugin.sys... ] Mark Struberg commented on CDI-50: ---------------------------------- To be honest: I for one am not so fond about @Veto and @Requires yet ... @Veto: completely underspecified! * How can it be modified via Extensions? * In which phase does it get applied? Directly at startup? Or only after ProcessAnnotatedType? * all corner cases and exceptional behaviour, e.g. how does it fit together with @New? @Requires: not user friendly * against JSR-250 * adds tons of NoClassDefFound pitfalls * how to prevent @Requires("wrongString") People should rather modularize their apps a bit better. > Ability to veto beans, both unconditionally and based on classes visible > ------------------------------------------------------------------------ > > Key: CDI-50 > URL: https://issues.jboss.org/browse/CDI-50 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Concepts, Packaging and Deployment > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1.EDR2 > > > This should support both a straight veto, and conditional based on classes available. > Seam Solder supports this as @Veto and @Requires({Foo.class, Bar.class}). > Mark Struberg proposed using @Optional -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-102) Support Injection of Servlet Contexts

by Romain Manni-Bucau (JIRA)

[ https://issues.jboss.org/browse/CDI-102?page=com.atlassian.jira.plugin.sy... ] Romain Manni-Bucau commented on CDI-102: ---------------------------------------- +1 for conflict, couldn't it be a kind of alternative to avoid to activate it when an extension is already here? (the feature is good btw but out of the box will break too much IMO) > Support Injection of Servlet Contexts > ------------------------------------- > > Key: CDI-102 > URL: https://issues.jboss.org/browse/CDI-102 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Priority: Minor > Fix For: 1.1.EDR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-102) Support Injection of Servlet Contexts

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-102?page=com.atlassian.jira.plugin.sy... ] Pete Muir commented on CDI-102: ------------------------------- This is a spec feature. Weld is already coupled to Servlet, so I'm not concerned about that. But the point about conflicting with existing extensions is relevant. Do you want to reopen? > Support Injection of Servlet Contexts > ------------------------------------- > > Key: CDI-102 > URL: https://issues.jboss.org/browse/CDI-102 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Priority: Minor > Fix For: 1.1.EDR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-102) Support Injection of Servlet Contexts

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/CDI-102?page=com.atlassian.jira.plugin.sy... ] Lincoln Baxter III commented on CDI-102: ---------------------------------------- Is this a Spec feature or just an extra Weld feature? I think this is bad either way. We are introducing more coupling between Weld and Servlet. The relationship here should be inverted IMO. This is causing bugs with apps that already wrote producers for Http**** artifacts. > Support Injection of Servlet Contexts > ------------------------------------- > > Key: CDI-102 > URL: https://issues.jboss.org/browse/CDI-102 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Priority: Minor > Fix For: 1.1.EDR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

ProcessSessionBean type declaration

by Martin Kouba

Hello everyone, does anyone know why ProcessSessionBean type declaration is "ProcessSessionBean<X> extends ProcessManagedBean<Object>" and not "ProcessSessionBean<X> extends ProcessManagedBean<X>"? Also there is no comment for type parameter X. Thanks Martin -- Martin Kouba JBoss Quality Assurance Engineer CDI TCK lead E-mail: mkouba(a)redhat.com Web: www.cz.redhat.com Red Hat Czech s.r.o., Purkyňova 99/71, 612 45, Brno, Czech Republic

12 years, 8 months

2
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev July 2012