December 2016 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-663) Usage of repeatable qualifiers contradicts several statements in the spec

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/CDI-663?page=com.atlassian.jira.plugin.sy... ] Tomas Remes updated CDI-663: ---------------------------- Fix Version/s: 2.0 .Final > Usage of repeatable qualifiers contradicts several statements in the spec > ------------------------------------------------------------------------- > > Key: CDI-663 > URL: https://issues.jboss.org/browse/CDI-663 > Project: CDI Specification Issues > Issue Type: Bug > Reporter: Tomas Remes > Fix For: 2.0 .Final > > > Using repeatable qualifier is in contradiction with {{11.3.12. Observer method resolution}}: > | If two instances of the same qualifier type are given, an IllegalArgumentException is thrown. > {{5.6.1. The Instance interface}}: > | If two instances of the same qualifier type are passed to select(), an IllegalArgumentException is thrown. > {{10.2.3. The Event interface}} > | If two instances of the same qualifier type are passed to select(), an llegalArgumentException is thrown. > {{11.3.6. Obtaining a Bean by type}} > | If two instances of the same qualifier type are given, an IllegalArgumentException is thrown. > {{11.3.13. Decorator resolution}} > | If two instances of the same qualifier type are given, an IllegalArgumentException is thrown. > {{11.3.14. Interceptor resolution}} > | If two instances of the same interceptor binding type are given, an IllegalArgumentException is thrown. > Should we remove this statement or make it more explicit by saying that this is true only for non-repeatable qualifiers/annotations? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (CDI-661) Annotated should return AnnotatedElement

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-661?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-661: ------------------------------------- Fix Version/s: 2.1 (Discussion) > Annotated should return AnnotatedElement > ---------------------------------------- > > Key: CDI-661 > URL: https://issues.jboss.org/browse/CDI-661 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Javadoc and API > Reporter: John Ament > Fix For: 2.1 (Discussion) > > > The {{Annotated}} interface returns a {{Type}} for its base type. It should return an {{AnnotatedElement}} based on its naming - since annotations are derived from {{AnnotatedElement}} s not from {{Type}} s -- 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)

[ https://issues.jboss.org/browse/CDI-656?page=com.atlassian.jira.plugin.sy... ] Work on CDI-656 started by Antoine Sabot-Durand. ------------------------------------------------ > 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 > Assignee: 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)

[ https://issues.jboss.org/browse/CDI-656?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand reassigned CDI-656: ---------------------------------------- Assignee: Antoine Sabot-Durand > 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 > Assignee: 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-662) Fix Instance.isResolvable() text and javadoc

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-662?page=com.atlassian.jira.plugin.sy... ] Martin Kouba reassigned CDI-662: -------------------------------- Assignee: Martin Kouba > Fix Instance.isResolvable() text and javadoc > -------------------------------------------- > > Key: CDI-662 > URL: https://issues.jboss.org/browse/CDI-662 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Martin Kouba > Assignee: Martin Kouba > Fix For: 2.0 .Final > > > A note that {{Instance.isResolvable()}} *IS* resolving ambiguities is missing in the spec text and javadoc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (CDI-662) Fix Instance.isResolvable() text and javadoc

by Martin Kouba (JIRA)

Martin Kouba created CDI-662: -------------------------------- Summary: Fix Instance.isResolvable() text and javadoc Key: CDI-662 URL: https://issues.jboss.org/browse/CDI-662 Project: CDI Specification Issues Issue Type: Clarification Reporter: Martin Kouba Fix For: 2.0 .Final A note that {{Instance.isResolvable()}} *IS* resolving ambiguities is missing in the spec text and javadoc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (CDI-593) Mention javax.enterprise.inject.spi.Prioritized in spec text and improve its javadoc

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-593?page=com.atlassian.jira.plugin.sy... ] Work on CDI-593 started by Antoine Sabot-Durand. ------------------------------------------------ > Mention javax.enterprise.inject.spi.Prioritized in spec text and improve its javadoc > ------------------------------------------------------------------------------------ > > Key: CDI-593 > URL: https://issues.jboss.org/browse/CDI-593 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Martin Kouba > Assignee: Antoine Sabot-Durand > Fix For: 2.0 .Final > > > * javadoc would definitely deserve some more info > * the spec text should mention this interface as well and describe basic use cases (e.g. an interceptor passed to {{AfterBeanDiscovery.addBean()}} and implementing this interface is globally enabled) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (CDI-232) Relax requirements for built-in Instance

by John Ament (JIRA)

[ https://issues.jboss.org/browse/CDI-232?page=com.atlassian.jira.plugin.sy... ] John Ament reassigned CDI-232: ------------------------------ Assignee: John Ament > Relax requirements for built-in Instance > ---------------------------------------- > > Key: CDI-232 > URL: https://issues.jboss.org/browse/CDI-232 > Project: CDI Specification Issues > Issue Type: Clarification > Affects Versions: 1.1.EDR > Reporter: Martin Kouba > Assignee: John Ament > Priority: Minor > Labels: F2F2016 > Fix For: 2.0 .Final > > > 5.6.2. The built-in Instance > {quote} > The container must provide a built-in bean with: > * Instance<X> and Provider<X> for every legal bean type X in its set of bean types, > * every qualifier type in its set of qualifier types, > {quote} > This type/qualifier requirements seem to be too strict. Maybe we should omit these and instead force implementation to satisfy every injection point for every legal bean type and corresponding qualifiers found in application... or something like that. I'm not sure about the wording. > By the way Weld (2.0.0.Alpha2) does not fulfil these requirements at the moment. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (CDI-658) Introduce ProducerConfigurator

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-658?page=com.atlassian.jira.plugin.sy... ] Martin Kouba updated CDI-658: ----------------------------- Fix Version/s: 2.0 .Final > Introduce ProducerConfigurator > ------------------------------ > > Key: CDI-658 > URL: https://issues.jboss.org/browse/CDI-658 > Project: CDI Specification Issues > Issue Type: Feature Request > Affects Versions: 2.0-EDR2 > Reporter: Antoine Sabot-Durand > Assignee: Martin Kouba > Fix For: 2.0 .Final > > > Configurator API lacks {{ProducerConfigurator}} it should be accessible from a new version of {{ProcessProducer.setProducer()}} method -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (CDI-658) Introduce ProducerConfigurator

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-658?page=com.atlassian.jira.plugin.sy... ] Martin Kouba reassigned CDI-658: -------------------------------- Assignee: Martin Kouba > Introduce ProducerConfigurator > ------------------------------ > > Key: CDI-658 > URL: https://issues.jboss.org/browse/CDI-658 > Project: CDI Specification Issues > Issue Type: Feature Request > Affects Versions: 2.0-EDR2 > Reporter: Antoine Sabot-Durand > Assignee: Martin Kouba > Fix For: 2.0 .Final > > > Configurator API lacks {{ProducerConfigurator}} it should be accessible from a new version of {{ProcessProducer.setProducer()}} method -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev December 2016