August 2012 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-92) Allow injection of Bean object for a bean

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-92?page=com.atlassian.jira.plugin.sys... ] Pete Muir commented on CDI-92: ------------------------------ I removed the part baked stuff that should be addressed properly in CDI-42, and fixed the remaining points in https://github.com/jboss/cdi/pull/69 > Allow injection of Bean object for a bean > ----------------------------------------- > > Key: CDI-92 > URL: https://issues.jboss.org/browse/CDI-92 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-56) Clarify that scope types should not have members

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-56?page=com.atlassian.jira.plugin.sys... ] Pete Muir resolved CDI-56. -------------------------- Fix Version/s: 1.1.EDR2 Resolution: Done I've made it non-portable to include members. As Mark indicates, this could be something interesting to experiment with. > Clarify that scope types should not have members > ------------------------------------------------ > > Key: CDI-56 > URL: https://issues.jboss.org/browse/CDI-56 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Concepts > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1.EDR2, 1.1.EDR1 > > > The spec should mention that @NormalScope annotations should not have annotation members. Perhaps this should be a definition error. javax.inject.Scope already mentions this. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-52) Make it clearer that an InjectionPoint injected into a disposer method refers to the producer method bean and not to the declaring bean

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-52?page=com.atlassian.jira.plugin.sys... ] Pete Muir commented on CDI-52: ------------------------------ Hmm, I'm not sure what we do here. This one came from Gavin originally, and I'm not sure what he was thinking of. > Make it clearer that an InjectionPoint injected into a disposer method refers to the producer method bean and not to the declaring bean > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: CDI-52 > URL: https://issues.jboss.org/browse/CDI-52 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Beans > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Priority: Critical > Fix For: 1.1.EDR2 > > -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-52) Make it clearer that an InjectionPoint injected into a disposer method refers to the producer method bean and not to the declaring bean

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-52?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-52: ------------------------- Priority: Critical (was: Major) > Make it clearer that an InjectionPoint injected into a disposer method refers to the producer method bean and not to the declaring bean > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: CDI-52 > URL: https://issues.jboss.org/browse/CDI-52 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Beans > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Priority: Critical > Fix For: 1.1.EDR2 > > -- 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

11 years, 8 months

1
0
0 / 0

CDI 1.1 weekly meeting

by pmuir＠redhat.com

The following is a new meeting request: Subject: CDI 1.1 weekly meeting Organiser: Peter Muir <pmuir(a)redhat.com> Time: 16:00:00 GMT+00:00 - 17:00:00 GMT+00:00 Recurrence: Every Monday. End by Aug 19, 2012. Effective Aug 13, 2012. Invitees: Mike Brock <cbrock(a)redhat.com>, "cdi-dev(a)lists.jboss.org" <cdi-dev(a)lists.jboss.org>, Joseph Bergmark/Durham/IBM <bergmark(a)us.ibm.com> *~*~*~*~*~*~*~*~*~* Weekly CDI 1.1 meeting http://www.timeanddate.com/worldclock/converted.html?iso=20120803T15&p1=0... We will try to use Google Hangout, join #jsr346 10 minutes before the meeting to request an invite. Otherwise switch to the phone teleconference, see https://docs.google.com/spreadsheet/pub?key=0ApqHbXzB1R1gdGRFWXB4TVpNeWFJ... for details.

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (CDI-152) Access the the web.xml from CDI extensions

by Brian Leathem (JIRA)

Access the the web.xml from CDI extensions ------------------------------------------ Key: CDI-152 URL: https://issues.jboss.org/browse/CDI-152 Project: CDI Specification Issues Issue Type: Feature Request Reporter: Brian Leathem Currently it is not possible to access the web.xml file from CDI extensions in a portable way, since the ServletContext is not available from CDI extensions (at least in EE enviroments). I filed a Servlet spec issue to make the web.xml file accessible, prior to the the ServletContext being initialized: http://java.net/jira/browse/SERVLET_SPEC-9 Perhaps as an alternative solution, CDI could do something to delay CDI extensions from loading until the ServletContext is available? Since this is the case for Servlet environments, would it not be acceptable for EE environments as well? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
3
0 / 0

[JBoss JIRA] (CDI-182) Cluster Lifecycle Events

by Kristoffer Sjögren (Created) (JIRA)

Cluster Lifecycle Events ------------------------ Key: CDI-182 URL: https://issues.jboss.org/browse/CDI-182 Project: CDI Specification Issues Issue Type: Feature Request Components: Events Affects Versions: 1.1 (Proposed) Environment: Any java environment. Reporter: Kristoffer Sjögren Priority: Minor Fix For: 1.1 (Proposed) CDI 1.1 defines a set of lifecycle events related to different context within the application. We see a need to also define cluster lifecycle events for applications. These events could, for example, be used for subscribing/allocating and unsubscribing/deallocating external services/resources. More specifically, a @Cluster event that gets fired when an application gets @Initialized in the cluster, that is, post @Application @Initialized. And another @Cluster event that gets fired when the application get @Destroyed in the cluster, that is, pre @Application @Destroyed. These events only fires once per application and cluster, independent on how many cluster instances exists. Events are fault tolerant meaning that events are not affected by failing instances going out-of-service, as long as the cluster is still working. Notice that the @Destroyed event is of course only invoked if the cluster terminates gracefully. -- 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

11 years, 8 months

2
1
0 / 0

[JBoss JIRA] (CDI-99) Obtain Extension instances from BeanManager

by Mark Struberg (JIRA)

[ https://issues.jboss.org/browse/CDI-99?page=com.atlassian.jira.plugin.sys... ] Mark Struberg commented on CDI-99: ---------------------------------- But it's not defined how many BeanManagers there are for a single (Web/Enterprise) Application... Think about hierarchic BeanManagers and stuff... > Obtain Extension instances from BeanManager > ------------------------------------------- > > Key: CDI-99 > URL: https://issues.jboss.org/browse/CDI-99 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Portable Extensions > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1.EDR2 > > -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (CDI-198) Make beans.xml validation consistent with the ProcessModule event

by Jozef Hartinger (Created) (JIRA)

Make beans.xml validation consistent with the ProcessModule event ----------------------------------------------------------------- Key: CDI-198 URL: https://issues.jboss.org/browse/CDI-198 Project: CDI Specification Issues Issue Type: Feature Request Components: Portable Extensions Affects Versions: 1.1.EDR1 Reporter: Jozef Hartinger Fix For: 1.1 (Proposed) The validation of enabled interceptors, alternatives and decorators is currently tightly related to the beans.xml file, e.g.: {quote}If the same class is listed twice under the <interceptors> element, the container automatically detects the problem and treats it as a deployment problem.{quote} With CDI-97 in place, which allows extensions to change the enabled alternatives, decorators and interceptors, this is no longer sufficient. IMO, the validation of enabled interceptors and decorators should be the following: 1.) For each deployment descriptor, the container verifies that it does not contain duplicate interceptors, decorators or alternatives. 2.) For each BDA, the container fires the ProcessModule event allowing extensions to modify enabled alternatives, interceptors and decorators. 3.) For each BDA, the container verifies that the resulting collection of enabled alternatives, decorators and interceptors does not contain duplicates. The step 1.) is not actually necessary but may be convenient. -- 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

11 years, 8 months

2
1
0 / 0

[JBoss JIRA] (CDI-99) Obtain Extension instances from BeanManager

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-99?page=com.atlassian.jira.plugin.sys... ] Pete Muir commented on CDI-99: ------------------------------ Jozef, how can this be ambiguous? There is one extension per extension class. > Obtain Extension instances from BeanManager > ------------------------------------------- > > Key: CDI-99 > URL: https://issues.jboss.org/browse/CDI-99 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Portable Extensions > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: 1.1.EDR2 > > -- 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

11 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev August 2012