August 2016 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-624) Map SeContainerInitializer.addBeans() and SeContainerInitializer.addAnnotatedTypes() to the application initialization lifecycle

by John Ament (JIRA)

[ https://issues.jboss.org/browse/CDI-624?page=com.atlassian.jira.plugin.sy... ] John Ament commented on CDI-624: -------------------------------- These methods must have snuck in. I was pushing hard against the idea of mixing container init and lifecycle in SE. I would prefer the dynamic extension approach, if anything were to be followed. > Map SeContainerInitializer.addBeans() and SeContainerInitializer.addAnnotatedTypes() to the application initialization lifecycle > -------------------------------------------------------------------------------------------------------------------------------- > > Key: CDI-624 > URL: https://issues.jboss.org/browse/CDI-624 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Java SE Integration > Affects Versions: 2.0-EDR2 > Reporter: Martin Kouba > > I believe we should not break the application initialization lifecycle. > So it might be reasonable to state that {{SeContainerInitializer.addAnnotatedTypes()}} maps to {{AfterTypeDiscovery.addAnnotatedType(AnnotatedType<?>, String)}} (note that we would have to sort out missing id) and {{SeContainerInitializer.addBeans()}} maps to {{AfterBeanDiscovery.addBean(Bean<?>)}}. > The other solution would be to remove these methods and introduce the concept of "synthetic container lifecycle event observers" and leverage the configurators API. See also http://weld.cdi-spec.org/news/2016/02/08/weld-se-synth-lifecycle-events/. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (CDI-624) Map SeContainerInitializer.addBeans() and SeContainerInitializer.addAnnotatedTypes() to the application initialization lifecycle

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/CDI-624?page=com.atlassian.jira.plugin.sy... ] Tomas Remes commented on CDI-624: --------------------------------- Personally I would adhere more to the second solution which seems to me more explicit and let's say "traditional". > Map SeContainerInitializer.addBeans() and SeContainerInitializer.addAnnotatedTypes() to the application initialization lifecycle > -------------------------------------------------------------------------------------------------------------------------------- > > Key: CDI-624 > URL: https://issues.jboss.org/browse/CDI-624 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Java SE Integration > Affects Versions: 2.0-EDR2 > Reporter: Martin Kouba > > I believe we should not break the application initialization lifecycle. > So it might be reasonable to state that {{SeContainerInitializer.addAnnotatedTypes()}} maps to {{AfterTypeDiscovery.addAnnotatedType(AnnotatedType<?>, String)}} (note that we would have to sort out missing id) and {{SeContainerInitializer.addBeans()}} maps to {{AfterBeanDiscovery.addBean(Bean<?>)}}. > The other solution would be to remove these methods and introduce the concept of "synthetic container lifecycle event observers" and leverage the configurators API. See also http://weld.cdi-spec.org/news/2016/02/08/weld-se-synth-lifecycle-events/. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (CDI-624) Map SeContainerInitializer.addBeans() and SeContainerInitializer.addAnnotatedTypes() to the application initialization lifecycle

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-624?page=com.atlassian.jira.plugin.sy... ] Martin Kouba updated CDI-624: ----------------------------- Component/s: Java SE Integration > Map SeContainerInitializer.addBeans() and SeContainerInitializer.addAnnotatedTypes() to the application initialization lifecycle > -------------------------------------------------------------------------------------------------------------------------------- > > Key: CDI-624 > URL: https://issues.jboss.org/browse/CDI-624 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Java SE Integration > Affects Versions: 2.0-EDR2 > Reporter: Martin Kouba > > I believe we should not break the application initialization lifecycle. > So it might be reasonable to state that {{SeContainerInitializer.addAnnotatedTypes()}} maps to {{AfterTypeDiscovery.addAnnotatedType(AnnotatedType<?>, String)}} (note that we would have to sort out missing id) and {{SeContainerInitializer.addBeans()}} maps to {{AfterBeanDiscovery.addBean(Bean<?>)}}. > The other solution would be to remove these methods and introduce the concept of "synthetic container lifecycle event observers" and leverage the configurators API. See also http://weld.cdi-spec.org/news/2016/02/08/weld-se-synth-lifecycle-events/. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (CDI-624) Map SeContainerInitializer.addBeans() and SeContainerInitializer.addAnnotatedTypes() to the application initialization lifecycle

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-624?page=com.atlassian.jira.plugin.sy... ] Martin Kouba updated CDI-624: ----------------------------- Affects Version/s: 2.0-EDR2 > Map SeContainerInitializer.addBeans() and SeContainerInitializer.addAnnotatedTypes() to the application initialization lifecycle > -------------------------------------------------------------------------------------------------------------------------------- > > Key: CDI-624 > URL: https://issues.jboss.org/browse/CDI-624 > Project: CDI Specification Issues > Issue Type: Clarification > Affects Versions: 2.0-EDR2 > Reporter: Martin Kouba > > I believe we should not break the application initialization lifecycle. > So it might be reasonable to state that {{SeContainerInitializer.addAnnotatedTypes()}} maps to {{AfterTypeDiscovery.addAnnotatedType(AnnotatedType<?>, String)}} (note that we would have to sort out missing id) and {{SeContainerInitializer.addBeans()}} maps to {{AfterBeanDiscovery.addBean(Bean<?>)}}. > The other solution would be to remove these methods and introduce the concept of "synthetic container lifecycle event observers" and leverage the configurators API. See also http://weld.cdi-spec.org/news/2016/02/08/weld-se-synth-lifecycle-events/. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (CDI-624) Map SeContainerInitializer.addBeans() and SeContainerInitializer.addAnnotatedTypes() to the application initialization lifecycle

by Martin Kouba (JIRA)

Martin Kouba created CDI-624: -------------------------------- Summary: Map SeContainerInitializer.addBeans() and SeContainerInitializer.addAnnotatedTypes() to the application initialization lifecycle Key: CDI-624 URL: https://issues.jboss.org/browse/CDI-624 Project: CDI Specification Issues Issue Type: Clarification Reporter: Martin Kouba I believe we should not break the application initialization lifecycle. So it might be reasonable to state that {{SeContainerInitializer.addAnnotatedTypes()}} maps to {{AfterTypeDiscovery.addAnnotatedType(AnnotatedType<?>, String)}} (note that we would have to sort out missing id) and {{SeContainerInitializer.addBeans()}} maps to {{AfterBeanDiscovery.addBean(Bean<?>)}}. The other solution would be to remove these methods and introduce the concept of "synthetic container lifecycle event observers" and leverage the configurators API. See also http://weld.cdi-spec.org/news/2016/02/08/weld-se-synth-lifecycle-events/. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

No meeting?

by John Ament

Antoine, Was today's meeting supposed to be canceled? John ________________________________ NOTICE: This e-mail message and any attachments may contain confidential, proprietary, and/or privileged information which should be treated accordingly. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this message, and destroy all physical and electronic copies. Thank you.

10 years

1
0
0 / 0

[JBoss JIRA] (CDI-541) Ordering of async observers (vs sync observers) is not specified

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-541?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-541: ------------------------------------- Fix Version/s: 2.0 (discussion) (was: 2.0-EDR2) > Ordering of async observers (vs sync observers) is not specified > ---------------------------------------------------------------- > > Key: CDI-541 > URL: https://issues.jboss.org/browse/CDI-541 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Events > Affects Versions: 2.0-EDR1 > Reporter: Tomas Remes > Fix For: 2.0 (discussion) > > > I think this needs to be specified. E.g. what happens if I fire async event and have more matching sync and async observers? Are all sync observes called first in given order with no regard to async observers priority? > For example: > {{event.fireAsync(new Message());}} > {code} > public class First { > > void observeMessage(@Observes @Priority(2000) Message message){} > } > {code} > {code} > public class Second { > > void observeMessage(@ObservesAsync @Priority(2100) Message message){} > } > {code} > {code} > public class Third { > > void observeMessage(@Observes @Priority(2200) Message message){} > } > {code} > {code} > public class Fourth { > > void observeMessage(@ObservesAsync @Priority(2300) Message message){} > } > {code} > What will be the order in this case? First, Third, Second, Fourth? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (CDI-612) ObserverMethodConfigurator.notifyWith() should probably accept a functional interface whose method throws java.lang.Exception

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-612?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-612: ------------------------------------- Fix Version/s: 2.0 (discussion) (was: 2.0-EDR2) > ObserverMethodConfigurator.notifyWith() should probably accept a functional interface whose method throws java.lang.Exception > ----------------------------------------------------------------------------------------------------------------------------- > > Key: CDI-612 > URL: https://issues.jboss.org/browse/CDI-612 > Project: CDI Specification Issues > Issue Type: Clarification > Affects Versions: 2.0-EDR1 > Reporter: Martin Kouba > Fix For: 2.0 (discussion) > > > The regular observer methods may also throw checked exceptions (wrapped and rethrown as an (unchecked) {{ObserverException}}). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (CDI-620) Not clear what the id for an annotated type is.

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-620?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-620: ------------------------------------- Fix Version/s: 2.0 (discussion) (was: 2.0-EDR2) > Not clear what the id for an annotated type is. > ----------------------------------------------- > > Key: CDI-620 > URL: https://issues.jboss.org/browse/CDI-620 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: John Ament > Fix For: 2.0 (discussion) > > > The docs for AfterTypeDiscovery.addAnnotatedType(String, Class) do not state what the id is. > In addition, it's odd that the addAnnotatedType(AnnotatedType, String) is in that order, and this method is in this order. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

Passed: cdi-spec/cdi#46 (master - b52a5f9)

by Travis CI

Build Update for cdi-spec/cdi ------------------------------------- Build: #46 Status: Passed Duration: 6 minutes and 19 seconds Commit: b52a5f9 (master) Author: Antoine Sabot-Durand Message: Prepare for development of 2.0-SNAPSHOT View the changeset: https://github.com/cdi-spec/cdi/compare/61a3d19384c1...b52a5f97aee2 View the full build log and details: https://travis-ci.org/cdi-spec/cdi/builds/150467705 -- You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications

10 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev August 2016