[cdi-dev] [JBoss JIRA] (CDI-165) Support lifecycle events for non-builtin contexts

Pete Muir (JIRA) jira-events at lists.jboss.org
Tue Aug 28 10:07:15 EDT 2012

     [ https://issues.jboss.org/browse/CDI-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Muir resolved CDI-165.

    Resolution: Done

> Support lifecycle events for non-builtin contexts
> -------------------------------------------------
>                 Key: CDI-165
>                 URL: https://issues.jboss.org/browse/CDI-165
>             Project: CDI Specification Issues
>          Issue Type: Feature Request
>          Components: Contexts
>    Affects Versions: 1.0
>            Reporter: Jozef Hartinger
>            Assignee: Pete Muir
>            Priority: Minor
>             Fix For: 1.1.PRD
> The original idea was to extend the API for context implementations to be able to notify the container of a context initialization / destruction. Based on this notification, the container would then notify the application by firing @Initialized(X) / @Destroyed(X) Object (where X is the scope annotation of the context - see CDI-86).
> I don't think this double-notification approach is a good idea anymore. Instead, the specification should simply mention that the extensions providing an implementation of Context are *encouraged* to fire a @Initialized(X) event when the context is initialized and @Destroyed(X) event when the context is destroyed (again, see CDI-86 for details). Extensions are free to choose a payload that makes most sense for the given context (e.g. UIViewRoot instance for @ViewScoped) or Object otherwise.

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


More information about the cdi-dev mailing list