November 2015 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-542) "10.2.2. Firing events asynchronously" update/enhancements

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-542?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-542: ------------------------------------- Fix Version/s: 2.0-EDR2 > "10.2.2. Firing events asynchronously" update/enhancements > ---------------------------------------------------------- > > Key: CDI-542 > URL: https://issues.jboss.org/browse/CDI-542 > Project: CDI Specification Issues > Issue Type: Feature Request > Affects Versions: 2.0-EDR1 > Reporter: Tomas Remes > Fix For: 2.0-EDR2 > > > This chapter (similar as the preceding) defines in general what does it mean to "fire an event" (sync vs async). Let say I am ordinary reader reading the spec from the beginning and I come to this chapter. > First of all I guess I will struggle little bit with the notion of ??resolved synchronous observers?? (vs ??resolved asynchronous observers??) > I think the following important information from "10.3. Observer resolution" could be mentioned earlier or some general description/example could be handy: > {quote} > * The event is fired synchronously and the observer is defined with @Observes. > * The event is fired asynchronously and the observer is defined with @Observes or @ObservesAsync. > {quote} > Second there is following sentence which TBH I have had fairly hard times to understand: > {quote} > If synchronous observer have to be notified, fireAsync returns immediately after the last synchronous observer has returned. Otherwise it returns immediately. > {quote} > ...and is IMO wrong. There should be "observers have to be" or "observer has to be" and it could be bit more explanatory. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-542) "10.2.2. Firing events asynchronously" update/enhancements

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-542?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand commented on CDI-542: ------------------------------------------ Don't panic Tomas, nobody read the spec ;). More seriously, you're right, what I propose is to link the observer resolution section to fire and fireasync section. Regarding the second point it has been corrected with CDI-564 > "10.2.2. Firing events asynchronously" update/enhancements > ---------------------------------------------------------- > > Key: CDI-542 > URL: https://issues.jboss.org/browse/CDI-542 > Project: CDI Specification Issues > Issue Type: Feature Request > Affects Versions: 2.0-EDR1 > Reporter: Tomas Remes > Fix For: 2.0-EDR2 > > > This chapter (similar as the preceding) defines in general what does it mean to "fire an event" (sync vs async). Let say I am ordinary reader reading the spec from the beginning and I come to this chapter. > First of all I guess I will struggle little bit with the notion of ??resolved synchronous observers?? (vs ??resolved asynchronous observers??) > I think the following important information from "10.3. Observer resolution" could be mentioned earlier or some general description/example could be handy: > {quote} > * The event is fired synchronously and the observer is defined with @Observes. > * The event is fired asynchronously and the observer is defined with @Observes or @ObservesAsync. > {quote} > Second there is following sentence which TBH I have had fairly hard times to understand: > {quote} > If synchronous observer have to be notified, fireAsync returns immediately after the last synchronous observer has returned. Otherwise it returns immediately. > {quote} > ...and is IMO wrong. There should be "observers have to be" or "observer has to be" and it could be bit more explanatory. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

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-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 > Priority: Major > Fix For: 2.0-EDR2 > > > 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)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-545) Clarify that observers can't be remote business method

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-545?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-545: ------------------------------------- Fix Version/s: 2.0-EDR2 > Clarify that observers can't be remote business method > ------------------------------------------------------- > > Key: CDI-545 > URL: https://issues.jboss.org/browse/CDI-545 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Java EE integration > Affects Versions: 1.2.Final > Reporter: Antoine Sabot-Durand > Priority: Major > Fix For: 2.0-EDR2 > > > In section 10.4 of 1.2 spec we have: > {quote} > If the bean is a session bean, the observer method must be either a business method of the EJB or a static method of the bean class. > {quote} > in 10.4.2 we also have: > {quote} > If a non-static method of a session bean class has a parameter annotated {{@Observes}}, and the method is not a business method of the EJB, the container automatically detects the problem and treats it as a definition error. > {quote} > This 2 assertions don't prevent an observer to be a business method of a remote client of an EJB. We should be more precise here and forbid this scenario. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

Updated Invitation: CDI weekly meeting @ Weekly from 18:00 to 19:00 on Tuesday except Tue Oct 6 18:00 or Tue Oct 13 18:00 (ASD Perso)

by antoine＠sabot-durand.net

This event has been changed. Title: CDI weekly meeting Weekly meeting of the CDI EG and other community members discussing CDI 2.0 specification. When: Weekly from 18:00 to 19:00 on Tuesday except Tue Oct 6 18:00 or Tue Oct 13 18:00 Paris (changed) Where: IRC #cdi-dev channel on freenode Calendar: ASD Perso Who: * Antoine Sabot-Durand - organizer * cdi-dev Event details: https://www.google.com/calendar/event?action=VIEW&eid=XzcxMGpnZ3BrNjEwaml... Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account cdi-dev(a)lists.jboss.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-558) Standardize the Meta-Data builders API (BeanBuilder, etc...)

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-558?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand edited comment on CDI-558 at 11/3/15 8:27 AM: ------------------------------------------------------------------- {quote}CDI SE builder may allow to access these builders - see my previous comment.{quote} Sorry, I missed that. {quote} bq. or if we decide later to allow addition of some meta data at runtime Well, if we decide later we could add this later. I think it's a good start to have it only accessible where it's needed ATM. {quote} Ok, but that doesn't solve the place for {{AnnotatedTypeBuilder}}. Should it be one of the few helpers classes of our API in {{javax.enterprise.util}} package beside {{AnnotationLiteral}}? was (Author: antoinesabot-durand): {quote}CDI SE builder may allow to access these builders - see my previous comment.{quote} Sorry, I missed that. {quote}{quote}or if we decide later to allow addition of some meta data at runtime{quote} Well, if we decide later we could add this later. I think it's a good start to have it only accessible where it's needed ATM. {quote} Ok, but that doesn't solve the place for {{AnnotatedTypeBuilder}}. Should it be one of the few helpers classes of our API in {{javax.enterprise.util}} package beside {{AnnotationLiteral}}? > Standardize the Meta-Data builders API (BeanBuilder, etc...) > ------------------------------------------------------------ > > Key: CDI-558 > URL: https://issues.jboss.org/browse/CDI-558 > Project: CDI Specification Issues > Issue Type: Feature Request > Reporter: Martin Kouba > Fix For: 2.0 (discussion) > > > The RI includes an experimental BeanBuilder API (see also http://weld.cdi-spec.org/news/2015/02/25/weld-300Alpha5/#_bean_builder_api for more information). The API is similar to the [API provided by DeltaSpike|http://deltaspike.apache.org/javadoc/1.2.1/org/apache/deltaspi...] but also includes some improvements (e.g. Java 8 lambdas may be used to simplify the process of registration). > * BeanBuilder Javadoc: http://docs.jboss.org/weld/javadoc/3.0/weld-api/org/jboss/weld/experiment... > * ExperimentalAfterBeanDiscovery Javadoc: http://docs.jboss.org/weld/javadoc/3.0/weld-api/org/jboss/weld/experiment... > * See also [the test extension for more examples of using this API|https://github.com/weld/core/blob/master/tests-arquillian/src/test/ja...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-558) Standardize the Meta-Data builders API (BeanBuilder, etc...)

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-558?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand commented on CDI-558: ------------------------------------------ {quote}CDI SE builder may allow to access these builders - see my previous comment.{quote} Sorry, I missed that. {quote}{quote}or if we decide later to allow addition of some meta data at runtime{quote} Well, if we decide later we could add this later. I think it's a good start to have it only accessible where it's needed ATM. {quote} Ok, but that doesn't solve the place for {{AnnotatedTypeBuilder}}. Should it be one of the few helpers classes of our API in {{javax.enterprise.util}} package beside {{AnnotationLiteral}}? > Standardize the Meta-Data builders API (BeanBuilder, etc...) > ------------------------------------------------------------ > > Key: CDI-558 > URL: https://issues.jboss.org/browse/CDI-558 > Project: CDI Specification Issues > Issue Type: Feature Request > Reporter: Martin Kouba > Fix For: 2.0 (discussion) > > > The RI includes an experimental BeanBuilder API (see also http://weld.cdi-spec.org/news/2015/02/25/weld-300Alpha5/#_bean_builder_api for more information). The API is similar to the [API provided by DeltaSpike|http://deltaspike.apache.org/javadoc/1.2.1/org/apache/deltaspi...] but also includes some improvements (e.g. Java 8 lambdas may be used to simplify the process of registration). > * BeanBuilder Javadoc: http://docs.jboss.org/weld/javadoc/3.0/weld-api/org/jboss/weld/experiment... > * ExperimentalAfterBeanDiscovery Javadoc: http://docs.jboss.org/weld/javadoc/3.0/weld-api/org/jboss/weld/experiment... > * See also [the test extension for more examples of using this API|https://github.com/weld/core/blob/master/tests-arquillian/src/test/ja...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-558) Standardize the Meta-Data builders API (BeanBuilder, etc...)

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-558?page=com.atlassian.jira.plugin.sy... ] Martin Kouba commented on CDI-558: ---------------------------------- bq. It doesn't solve the problem of having a place to put AnnotatedTypeBuilder It's true, on the other hand the AnnotatedTypeBuilder would be a bit special, i.e. it doesn't need a {{BeanManager}} instance unlike BeanBuilder using BM e.g. to create {{InjectionTarget}}. bq. The use could be to create a bean and use it in launching the container in SE CDI SE builder may allow to access these builders - see my previous comment. bq. or if we decide later to allow addition of some meta data at runtime Well, if we decide later we could add this later. I think it's a good start to have it only accessible where it's needed ATM. > Standardize the Meta-Data builders API (BeanBuilder, etc...) > ------------------------------------------------------------ > > Key: CDI-558 > URL: https://issues.jboss.org/browse/CDI-558 > Project: CDI Specification Issues > Issue Type: Feature Request > Reporter: Martin Kouba > Fix For: 2.0 (discussion) > > > The RI includes an experimental BeanBuilder API (see also http://weld.cdi-spec.org/news/2015/02/25/weld-300Alpha5/#_bean_builder_api for more information). The API is similar to the [API provided by DeltaSpike|http://deltaspike.apache.org/javadoc/1.2.1/org/apache/deltaspi...] but also includes some improvements (e.g. Java 8 lambdas may be used to simplify the process of registration). > * BeanBuilder Javadoc: http://docs.jboss.org/weld/javadoc/3.0/weld-api/org/jboss/weld/experiment... > * ExperimentalAfterBeanDiscovery Javadoc: http://docs.jboss.org/weld/javadoc/3.0/weld-api/org/jboss/weld/experiment... > * See also [the test extension for more examples of using this API|https://github.com/weld/core/blob/master/tests-arquillian/src/test/ja...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-558) Standardize the Meta-Data builders API (BeanBuilder, etc...)

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-558?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand commented on CDI-558: ------------------------------------------ I have 3 concerns by having these accessible only in lifecycle event: * Consistency: why having some accessible in events and others elsewhere * It doesn't solve the problem of having a place to put AnnotatedTypeBuilder * It prevents creation of these meta data from outside CDI. The use could be to create a bean and use it in launching the container in SE or if we decide later to allow addition of some meta data at runtime. > Standardize the Meta-Data builders API (BeanBuilder, etc...) > ------------------------------------------------------------ > > Key: CDI-558 > URL: https://issues.jboss.org/browse/CDI-558 > Project: CDI Specification Issues > Issue Type: Feature Request > Reporter: Martin Kouba > Fix For: 2.0 (discussion) > > > The RI includes an experimental BeanBuilder API (see also http://weld.cdi-spec.org/news/2015/02/25/weld-300Alpha5/#_bean_builder_api for more information). The API is similar to the [API provided by DeltaSpike|http://deltaspike.apache.org/javadoc/1.2.1/org/apache/deltaspi...] but also includes some improvements (e.g. Java 8 lambdas may be used to simplify the process of registration). > * BeanBuilder Javadoc: http://docs.jboss.org/weld/javadoc/3.0/weld-api/org/jboss/weld/experiment... > * ExperimentalAfterBeanDiscovery Javadoc: http://docs.jboss.org/weld/javadoc/3.0/weld-api/org/jboss/weld/experiment... > * See also [the test extension for more examples of using this API|https://github.com/weld/core/blob/master/tests-arquillian/src/test/ja...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

Tomorrow's meeting agenda

by Antoine Sabot-Durand

Hi all, Tomorrow I'd like to talk about: - Java One feedback - https://issues.jboss.org/browse/CDI-558 : Metadata builder - https://issues.jboss.org/browse/CDI-568: Se bootstrap API evolution - AOP on producer / custom bean If you have other topic, feel free to send them. Regards, Antoine

8 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev November 2015