cdi-dev September 2016

cdi-dev@lists.jboss.org

11 participants
173 discussions

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

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-625?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-625: ------------------------------------- Fix Version/s: 2.0 (proposed) (was: 2.0 (discussion)) > 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 {{(a)Initialized(X.class)}} is fired when a context is initialized and {{(a)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: > * {{(a)Initialized(X.class)}} is fired *after the initialization* of a context is finished, i.e. the context is ready? > * {{(a)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 {{(a)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 {{(a)Destroyed(X.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)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-626) How should CDI.current() and CDI.getBeanManager() behave for non-CDI apps?

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-626?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-626: ------------------------------------- Fix Version/s: 2.0 (proposed) (was: 2.0 (discussion)) > How should CDI.current() and CDI.getBeanManager() behave for non-CDI apps? > -------------------------------------------------------------------------- > > Key: CDI-626 > URL: https://issues.jboss.org/browse/CDI-626 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Mark Struberg > Labels: F2F2016 > Fix For: 2.0 (proposed) > > > We did hit the following situation: > A user installs a Spring application WAR file in TomEE. In that case we don't boot the CDI container. But the JSF Container calls CDI.current(). > How should CDI.current() behave in that case? Throwing an IllegalStateException, returning null or return a non-functional BeanManager? > We should also define the behaviour of CDI.getBeanManager while we are at it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-415) Observer resolution doesn't specify handling of null parameter values

by Michael Kotten (JIRA)

[ https://issues.jboss.org/browse/CDI-415?page=com.atlassian.jira.plugin.sy... ] Michael Kotten commented on CDI-415: ------------------------------------ It should be explicitly stated that _null_ is a non valid value for an event. In the end this might be, because you can't extract the type of _null_. BTW, OWB just crashes with a NPE when calling getClass() ;-). > Observer resolution doesn't specify handling of null parameter values > --------------------------------------------------------------------- > > Key: CDI-415 > URL: https://issues.jboss.org/browse/CDI-415 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Events > Reporter: Michael Kotten > Priority: Minor > Labels: F2F2016 > Fix For: 2.0 (discussion) > > > There is a gap in chapter 10.2 of the current CDI spec about [observer resolution|http://docs.jboss.org/cdi/spec/1.1/cdi-spec.html#observer_reso...]. It doesn't specify what should happen if an event gets fired using a null value. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

← Newer
1
...
15
16
17
18
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev September 2016