[cdi-dev] [JBoss JIRA] (CDI-625) When exactly are events with @Initialized(X.class) and @Destroyed(X.class) qualifiers fired

[Romain Manni-Bucau (JIRA)]

    [ https://issues.jboss.org/browse/CDI-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291173#comment-13291173 ] 

Romain Manni-Bucau edited comment on CDI-625 at 9/9/16 8:54 AM:
----------------------------------------------------------------

idea would be to have a default phase and allow to have a kind of interceptor for the event which would lead to the final proceed being the actual action. You can see it as the context.destroy() being intercepted by observers.

Idea was:

{code:java}
public void around(@Observes @Destroyed(X.class) EventContext<Object> ctx) {
   // before context.destroy();
   ctx.proceed(); // actual destroy
   // after context.destroy(), often in finally
}
{code}

Concretely it would give a way to have interceptor feature on events which would enable to have interceptor-like on not managed beans. Built-in events could benefit from it.


was (Author: rmannibucau):
idea would be to have a default phase and allow to have a kind of interceptor for the event which would lead to the final proceed being the actual action. You can see it as the context.destroy() being intercepted by observers.

Idea was:

{code:java}
public void around(@Observes @Destroyed(X.class) EventContext<Object> ctx) {
   // before context.destroy();
   ctx.proceed(); // actual destroy
   // after context, often in finally
}
{code}

Concretely it would give a way to have interceptor feature on events which would enable to have interceptor-like on not managed beans. Built-in events could benefit from it.

> When exactly are events with @Initialized(X.class) and @Destroyed(X.class) qualifiers fired
> -------------------------------------------------------------------------------------------
>
>                 Key: CDI-625
>                 URL: https://issues.jboss.org/browse/CDI-625
>             Project: CDI Specification Issues
>          Issue Type: Clarification
>          Components: Events
>            Reporter: Martin Kouba
>              Labels: F2F2016
>             Fix For: 2.0 (proposed)
>
>
> The spec states that {{@Initialized(X.class)}} is fired when a context is initialized and {{@Destroyed(X.class)}} when a context is destroyed (note that for {{@ApplicationScoped}} the wording leaves out the context: _"when the application is destroyed"_). 
> Does it mean that:
> * {{@Initialized(X.class)}} is fired *after the initialization* of a context is finished, i.e. the context is ready?
> * {{@Destroyed(X.class)}} is fired *after the destruction* of a context is finished, i.e. after all the beans are destroyed?
> I'm asking because for {{@Destroyed(X.class)}} it might be useful to perform some cleanup before the context is actually destroyed - see also CDI-601.
> In RI/Weld, the behaivour of {{@Destroyed(ApplicationScoped.class)}} is currently a little bit inconsistent. For webapps and Weld SE, the event is fired before the context is destroyed. But for non-web EE modules (e.g. ejb jar) the event is fired after the context is destroyed.
> I believe this should be more clear.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)