[
https://issues.jboss.org/browse/CDI-165?page=com.atlassian.jira.plugin.sy...
]
Jozef Hartinger updated CDI-165:
--------------------------------
Description:
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.
was:
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.
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
Priority: Minor
Fix For: 1.1 (Proposed)
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.
For more information on JIRA, see:
http://www.atlassian.com/software/jira