June 2011 - cdi-dev - Jboss List Archives

by Pete Muir

A number of people have requested that CDI fire lifecycle events. I have produced the following proposal to start a discussion: ================================================ Add these qualifiers: • @Initialized • @Destroyed • @Application • @Session • @Conversation • @Request And require that the container fires an event with an event type of Object when a context is initialized and destroyed, giving us 8 distinct events: • @Initialized @Application Object o; • @Destroyed @Application Object o; • @Initialized @Session Object o; • @Destroyed @Session Object o; • @Initialized @Conversation Object o; • @Destroyed @Conversation Object o; • @Initialized @Request Object o; • @Destroyed @Request Object o; The payload of the event will depend on the environment in which CDI is operating. The spec would require that if the application was a web application that the payload would be the relevant event as defined by the Servlet spec. The @Application event would be deferred until bootstrap is complete. ================================================ This will require the support of the Platform EG, so once we have a proposal we like, I will take it to them. WDYT? Pete

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (CDI-86) Support firing general purpose lifecycle events in Java EE environments

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-86?page=com.atlassian.jira.plugin.sys... ] Pete Muir commented on CDI-86: ------------------------------ h1. Proposal Add these qualifiers: * {{@Initialized}} * {{@Destroyed}} * {{@Application}} * {{@Session}} * {{@Conversation}} * {{@Request}} And require that the container fires an event with an event type of Object when a context is initialized and destroyed, giving us 8 distinct events: * {{@Initialized @Application Object o;}} * {{@Destroyed @Application Object o;}} * {{@Initialized @Session Object o;}} * {{@Destroyed @Session Object o;}} * {{@Initialized @Conversation Object o;}} * {{@Destroyed @Conversation Object o;}} * {{@Initialized @Request Object o;}} * {{@Destroyed @Request Object o;}} The payload of the event will depend on the environment in which CDI is operating. The spec would require that if the application was a web application that the payload would be the relevant event as defined by the Servlet spec. The @Application event would be deferred until bootstrap is complete. > Support firing general purpose lifecycle events in Java EE environments > ----------------------------------------------------------------------- > > Key: CDI-86 > URL: https://issues.jboss.org/browse/CDI-86 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: 1.1 (Proposed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (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 updated CDI-102: -------------------------- Assignee: Pete Muir Fix Version/s: 1.1 (Confirmed) (was: 1.1 (Proposed)) Priority: Minor (was: Major) Forum Reference: http://www.seamframework.org/Weld/JavaEEIntegrationWishlist#H-SupportInje... (was: http://www.seamframework.org/Weld/JavaEEIntegrationWishlist#H-SupportInje...) > 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 (Confirmed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (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: ------------------------------- https://github.com/jboss/cdi/pull/36 > 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 > Fix For: 1.1 (Confirmed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-36) ObserverMethod.notify() does not forward qualifiers for Event

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-36?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-36: ------------------------- Assignee: Pete Muir Fix Version/s: 1.1 (Confirmed) (was: 1.1 (Proposed)) > ObserverMethod.notify() does not forward qualifiers for Event > ------------------------------------------------------------- > > Key: CDI-36 > URL: https://issues.jboss.org/browse/CDI-36 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Events > Affects Versions: 1.0 > Reporter: Jordan Ganoff > Assignee: Pete Muir > Fix For: 1.1 (Confirmed) > > > There's currently no way to get the qualifiers for a fired event. ObserverMethod.notify() only passes the event object itself. Without the qualifiers it is difficult to bridge the gap between CDI events and some other event infrastructure (e.g. JMS). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (CDI-36) ObserverMethod.notify() does not forward qualifiers for Event

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-36?page=com.atlassian.jira.plugin.sys... ] Pete Muir commented on CDI-36: ------------------------------ https://github.com/jboss/cdi/pull/35 > ObserverMethod.notify() does not forward qualifiers for Event > ------------------------------------------------------------- > > Key: CDI-36 > URL: https://issues.jboss.org/browse/CDI-36 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Events > Affects Versions: 1.0 > Reporter: Jordan Ganoff > Fix For: 1.1 (Confirmed) > > > There's currently no way to get the qualifiers for a fired event. ObserverMethod.notify() only passes the event object itself. Without the qualifiers it is difficult to bridge the gap between CDI events and some other event infrastructure (e.g. JMS). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Assigned: (CDI-85) Clarify use of "to" and "from" when refering to assignments in section 5.2.3

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-85?page=com.atlassian.jira.plugin.sys... ] Pete Muir reassigned CDI-85: ---------------------------- Assignee: Pete Muir > Clarify use of "to" and "from" when refering to assignments in section 5.2.3 > ---------------------------------------------------------------------------- > > Key: CDI-85 > URL: https://issues.jboss.org/browse/CDI-85 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Resolution > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Priority: Minor > Fix For: 1.1 (Confirmed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (CDI-85) Clarify use of "to" and "from" when refering to assignments in section 5.2.3

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-85?page=com.atlassian.jira.plugin.sys... ] Pete Muir commented on CDI-85: ------------------------------ https://github.com/jboss/cdi/pull/34 > Clarify use of "to" and "from" when refering to assignments in section 5.2.3 > ---------------------------------------------------------------------------- > > Key: CDI-85 > URL: https://issues.jboss.org/browse/CDI-85 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Resolution > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: 1.1 (Confirmed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-85) Clarify use of "to" and "from" when refering to assignments in section 5.2.3

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-85?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-85: ------------------------- Fix Version/s: 1.1 (Confirmed) (was: 1.1 (Proposed)) Priority: Minor (was: Major) Forum Reference: http://lists.jboss.org/pipermail/weld-dev/2010-August/002627.html (was: http://lists.jboss.org/pipermail/weld-dev/2010-August/002627.html) > Clarify use of "to" and "from" when refering to assignments in section 5.2.3 > ---------------------------------------------------------------------------- > > Key: CDI-85 > URL: https://issues.jboss.org/browse/CDI-85 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Resolution > Affects Versions: 1.0 > Reporter: Pete Muir > Priority: Minor > Fix For: 1.1 (Confirmed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (CDI-83) Clarify that BeanManager.createAnnotatedType() should return any modifications made by lifecycle events.

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-83?page=com.atlassian.jira.plugin.sys... ] Pete Muir updated CDI-83: ------------------------- Forum Reference: http://lists.jboss.org/pipermail/weld-dev/2010-May/002499.html (was: http://lists.jboss.org/pipermail/weld-dev/2010-May/002499.html) https://github.com/jboss/cdi/pull/33 > Clarify that BeanManager.createAnnotatedType() should return any modifications made by lifecycle events. > -------------------------------------------------------------------------------------------------------- > > Key: CDI-83 > URL: https://issues.jboss.org/browse/CDI-83 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Portable Extensions > Affects Versions: 1.0 > Reporter: Pete Muir > Fix For: 1.1 (Confirmed) > > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev June 2011