December 2016 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-656) Clarify effect of @Priority on ordered observers

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-656?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-656: ------------------------------------- Fix Version/s: 2.0 .Final > Clarify effect of @Priority on ordered observers > ------------------------------------------------ > > Key: CDI-656 > URL: https://issues.jboss.org/browse/CDI-656 > Project: CDI Specification Issues > Issue Type: Clarification > Affects Versions: 2.0-EDR2 > Reporter: Antoine Sabot-Durand > Fix For: 2.0 .Final > > > Effect of adding {{@Priority}} on an async observer is not specified in the spec. We should state that in that case "non-portable behavior results" -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (CDI-656) Clarify effect of @Priority on ordered observers

by Antoine Sabot-Durand (JIRA)

Antoine Sabot-Durand created CDI-656: ---------------------------------------- Summary: Clarify effect of @Priority on ordered observers Key: CDI-656 URL: https://issues.jboss.org/browse/CDI-656 Project: CDI Specification Issues Issue Type: Clarification Affects Versions: 2.0-EDR2 Reporter: Antoine Sabot-Durand Effect of adding {{@Priority}} on an async observer is not specified in the spec. We should state that in that case "non-portable behavior results" -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

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

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-541?page=com.atlassian.jira.plugin.sy... ] Martin Kouba commented on CDI-541: ---------------------------------- [~antoinesabot-durand] Even if we move this to 2.1 we should clarify that async observer with priority results in "non-portable behavior non-portable in 2.0! > 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.1 (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 (v7.2.3#72005)

8 years, 1 month

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 commented on CDI-541: ------------------------------------------ I propose that we move ordering of async observer to 2.1. > 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.1 (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 (v7.2.3#72005)

8 years, 1 month

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.1 (Discussion) (was: 2.0 .Final) > 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.1 (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 (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (CDI-471) Support repeating qualifiers

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-471?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand reopened CDI-471: -------------------------------------- > Support repeating qualifiers > ---------------------------- > > Key: CDI-471 > URL: https://issues.jboss.org/browse/CDI-471 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Resolution > Reporter: Antonin Stefanutti > Assignee: John Ament > Labels: F2F2016 > Fix For: 2.0 .Final > > > As Java 8 provides improved support for [repeating annotations|http://docs.oracle.com/javase/tutorial/java/annotations/repea...], it would be valuable to percolate that support into the CDI typesafe resolution mechanism. > For example, one could write: > {code} > @Qualifier > @Repeatable(ContextNames.class) > public interface @ContextName { > String value; > } > public @interface ContextNames { > ContextName[] value(); > } > {code} > And then: > {code} > @ContextName("ctx1") > class CamelContext1 { > } > @ContextName("ctx2") > class CamelContext2 { > } > @Uri("") > @Produces > @ContextName("ctx1") > @ContextName("ctx2") > static ProducerTemplate producerTemplate(InjectionPoint ip, @Any Instance<CamelContext> instance) { > } > {code} > That enables to use annotations both as a CDI qualifiers and a metadata providers while still be relying on standard typesafe resolution mechanism during the deployment phase to detect unsatisfied or ambiguous dependencies. > Support of the annotation container / list for backward compatibility could be provided as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (CDI-652) Introduce example of InterceptionFactory usage in 11.7. Apply interceptor programmatically

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-652?page=com.atlassian.jira.plugin.sy... ] Martin Kouba reassigned CDI-652: -------------------------------- Assignee: Tomas Remes > Introduce example of InterceptionFactory usage in 11.7. Apply interceptor programmatically > ------------------------------------------------------------------------------------------ > > Key: CDI-652 > URL: https://issues.jboss.org/browse/CDI-652 > Project: CDI Specification Issues > Issue Type: Feature Request > Reporter: Tomas Remes > Assignee: Tomas Remes > Fix For: 2.0 .Final > > > This new feature would deserve some example in related chapter IMO: -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev December 2016