April 2015 - cdi-dev - Jboss List Archives

by Mark Struberg

Hi! The CDI-1.2 spec says in 6.7.3: „An event with qualifier @Initialized(ApplicationScoped.class) is fired when the application context is initialized and an event with qualifier @Destroyed(ApplicationScoped.class) is fired when the application is destroyed. " Now from the pure wording („IS initialized“, „IS destroyed“) I’d say that both events must be fired _after_ the state is reached. Means _after_ the context got initialized and _after_ the context got destroyed. Means an observer like @ApplicationScoped public class MyBean { public void endIt(@Observes @Destroyed(ApplicationScoped.class) endObject) { doSomething() } } will _never_ get invoked. Because the bean (and the whole context) will be already killed… You can observe this event in a @Singleton scoped bean, but not in an @ApplicationScoped bean. If you like to do _that_, then simply use a @PreDestroy. Do others share this interpretation? Do we need to clarify anything? LieGrue, strub

9 years, 7 months

4
4
0 / 0

[JBoss JIRA] (CDI-520) 3.6. Java EE components

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-520?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-520: ------------------------------------- Fix Version/s: TBD > 3.6. Java EE components > ----------------------- > > Key: CDI-520 > URL: https://issues.jboss.org/browse/CDI-520 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Java EE integration > Affects Versions: 1.1.Final > Reporter: Martin Andersson > Fix For: TBD > > > I don't understand this text: > "The instance used by the container to service an invocation of a Java EE component will not be the same instance obtained when using @Inject, instantiated by the container to invoke a producer method, observer method or disposer method, or instantiated by the container to access the value of a producer field." > More specifically, I am trying to understand how we can use CDI to put a scope on {{EntityManager}} whose life cycle is rather undefined by JPA. I see that the specification use an example of a {{@Disposes}} method to close a container-managed entity manager which throw {{IllegalStateException}} in the disposer (!). Anyways, trying to solve this puzzle has led me to the paragraph quoted previously, of which I understand nothing to be honest. > My research about the "CDI managed container-managed entity manager" continues. As of now, the example is flawed and a container-managed entity manager remains open after the disposer method. Anyways, I might open up a separate ticket for that. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-522) Create add method setObserver() to ProcessObserverMethod SPI event

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-522?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-522: ------------------------------------- Fix Version/s: 2.0 (discussion) > Create add method setObserver() to ProcessObserverMethod SPI event > ------------------------------------------------------------------ > > Key: CDI-522 > URL: https://issues.jboss.org/browse/CDI-522 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Events > Affects Versions: 1.2.Final > Reporter: Antoine Sabot-Durand > Fix For: 2.0 (discussion) > > > Right now {{ObserverMethod}} cannot be change in an extension. In the philosophy of {{ProcessAnnotatedType#setAnnotatedType}} or {{ProcessBeanAttributes#setBeanAttributes}} we could add a {{ProcessObserverMethod#setObserverMethod}} to change properties on an observer. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

Using StartMain

by Michael Remijan

cdi-dev, With the SE Bootstrap standardization in works, I wondering if org.jboss.weld.environment.se.StartMain is still going to be supported, or, possibly something similar added to the CDI api itself. Having a standard way to bootstrap CDI is great but org.jboss.weld.environment.se.StartMain is even better because I'd say in most cases I don't want to start the container myself I just want it up, running, and available for use in my application. Just a thought.

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-522) Create add method setObserver() to ProcessObserverMethod SPI event

by Antoine Sabot-Durand (JIRA)

Antoine Sabot-Durand created CDI-522: ---------------------------------------- Summary: Create add method setObserver() to ProcessObserverMethod SPI event Key: CDI-522 URL: https://issues.jboss.org/browse/CDI-522 Project: CDI Specification Issues Issue Type: Feature Request Components: Events Affects Versions: 1.2.Final Reporter: Antoine Sabot-Durand Right now {{ObserverMethod}} cannot be change in an extension. In the philosophy of {{ProcessAnnotatedType#setAnnotatedType}} or {{ProcessBeanAttributes#setBeanAttributes}} we could add a {{ProcessObserverMethod#setObserverMethod}} to change properties on an observer. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-521) Create a Prioritized Interface for SPI element that have a priority

by Antoine Sabot-Durand (JIRA)

Antoine Sabot-Durand created CDI-521: ---------------------------------------- Summary: Create a Prioritized Interface for SPI element that have a priority Key: CDI-521 URL: https://issues.jboss.org/browse/CDI-521 Project: CDI Specification Issues Issue Type: Feature Request Components: Concepts Affects Versions: 1.2.Final Reporter: Antoine Sabot-Durand With the addition of ordering in Observer (CDI-4), we have a collection of element in SPI that could benefit having a {{getPriority()}} method: * {{ObserverMethod}} * {{Bean}} to be able to read alternative priority and give priority for {{Decorator}} and {{Interceptor}} Any other place? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-521) Create a Prioritized Interface for SPI element that have a priority

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-521?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-521: ------------------------------------- Fix Version/s: 2.0 (discussion) > Create a Prioritized Interface for SPI element that have a priority > -------------------------------------------------------------------- > > Key: CDI-521 > URL: https://issues.jboss.org/browse/CDI-521 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Concepts > Affects Versions: 1.2.Final > Reporter: Antoine Sabot-Durand > Fix For: 2.0 (discussion) > > > With the addition of ordering in Observer (CDI-4), we have a collection of element in SPI that could benefit having a {{getPriority()}} method: > * {{ObserverMethod}} > * {{Bean}} to be able to read alternative priority and give priority for {{Decorator}} and {{Interceptor}} > Any other place? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 7 months

1
0
0 / 0

yesterday meeting

by Antoine Sabot-Durand

Hi all, In yesterday meeting we discuss about ordering event proposal. Meeting summary is here: http://transcripts.jboss.org/meeting/irc.freenode.org/cdi-dev/2015/cdi-de... <http://transcripts.jboss.org/meeting/irc.freenode.org/cdi-dev/2015/cdi-de...> Antoine

9 years, 7 months

1
0
0 / 0

Bootstrap API in Weld 3.0.0.Alpha8

by Jozef Hartinger

We extended Weld's API for Java SE in the recent 3.0.0.Alpha8 release. The main feature is a new builder for programmatic configuration of managed classes, packages, enabled interceptors and others. This could serve as a draft for the bootstrap API to be added to CDI. See the release blog post for more details: http://weld.cdi-spec.org/news/2015/04/21/weld-300Alpha8/ Jozef

9 years, 7 months

4
5
0 / 0

Update on Java EE/SE split

by Antoine Sabot-Durand

Hi all, I corrected some points on the split in https://github.com/cdi-spec/cdi/pull/241 <https://github.com/cdi-spec/cdi/pull/241> There are still things to correct. I’ll do a recap this week. After discussing with Pete, I renamed the first part to CDI core and introduced a new part for Java SE. So the spec is now: - CDI Core (feature present in SE and EE) - CDI in SE (will contains SE bootstrap and specific bean discovery stuff) - CDI in EE The new spec draft is available here : https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html <https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html> I’ll continue working on it this week, but your feedback and proposal to improve this split is always welcome. Antoine

9 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev April 2015