August 2016 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-471) Support repeating qualifiers in typesafe resolution mechanism

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-471?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand commented on CDI-471: ------------------------------------------ yes, it's on my list ;). > Support repeating qualifiers in typesafe resolution mechanism > ------------------------------------------------------------- > > Key: CDI-471 > URL: https://issues.jboss.org/browse/CDI-471 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Resolution > Reporter: Antonin Stefanutti > Labels: F2F2016 > > 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 (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

Cancelling meeting today

by Antoine Sabot-Durand

Sorry, guys, I've got still a lot of work to do to prepare next week F2F meeting and Java One Talks and meeting with other specs. Antoine

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (CDI-471) Support repeating qualifiers in typesafe resolution mechanism

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-471?page=com.atlassian.jira.plugin.sy... ] Martin Kouba updated CDI-471: ----------------------------- Labels: F2F2016 (was: ) > Support repeating qualifiers in typesafe resolution mechanism > ------------------------------------------------------------- > > Key: CDI-471 > URL: https://issues.jboss.org/browse/CDI-471 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Resolution > Reporter: Antonin Stefanutti > Labels: F2F2016 > > 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 (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (CDI-471) Support repeating qualifiers in typesafe resolution mechanism

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/CDI-471?page=com.atlassian.jira.plugin.sy... ] Tomas Remes edited comment on CDI-471 at 8/30/16 9:20 AM: ---------------------------------------------------------- [~antoinesabot-durand] I think this should be one of the issues with highest priority for upcoming CDI F2F meeting. WDYT? was (Author: tremes): [~antoinesabot-durand] I think this should one of the issues with highest priority for upcoming CDI F2F meeting. WDYT? > Support repeating qualifiers in typesafe resolution mechanism > ------------------------------------------------------------- > > Key: CDI-471 > URL: https://issues.jboss.org/browse/CDI-471 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Resolution > Reporter: Antonin Stefanutti > > 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 (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (CDI-471) Support repeating qualifiers in typesafe resolution mechanism

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/CDI-471?page=com.atlassian.jira.plugin.sy... ] Tomas Remes commented on CDI-471: --------------------------------- [~antoinesabot-durand] I think this should one of the issues with highest priority for upcoming CDI F2F meeting. WDYT? > Support repeating qualifiers in typesafe resolution mechanism > ------------------------------------------------------------- > > Key: CDI-471 > URL: https://issues.jboss.org/browse/CDI-471 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Resolution > Reporter: Antonin Stefanutti > > 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 (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (CDI-415) Observer resolution doesn't specify handling of null parameter values

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-415?page=com.atlassian.jira.plugin.sy... ] Martin Kouba commented on CDI-415: ---------------------------------- Weld throws an {{IllegalArgumentException}} which is fine IMHO. Also I don't think this requires spec text change, a javadoc update would be enough. > Observer resolution doesn't specify handling of null parameter values > --------------------------------------------------------------------- > > Key: CDI-415 > URL: https://issues.jboss.org/browse/CDI-415 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Events > Reporter: Michael Kotten > Priority: Minor > Labels: F2F2016 > Fix For: 2.0 (discussion) > > > There is a gap in chapter 10.2 of the current CDI spec about [observer resolution|http://docs.jboss.org/cdi/spec/1.1/cdi-spec.html#observer_reso...]. It doesn't specify what should happen if an event gets fired using a null value. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (CDI-626) How should CDI.current() and CDI.getBeanManager() behave for non-CDI apps?

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-626?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-626: ------------------------------------- Labels: F2F2016 (was: ) > How should CDI.current() and CDI.getBeanManager() behave for non-CDI apps? > -------------------------------------------------------------------------- > > Key: CDI-626 > URL: https://issues.jboss.org/browse/CDI-626 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Mark Struberg > Labels: F2F2016 > Fix For: 2.0 (discussion) > > > We did hit the following situation: > A user installs a Spring application WAR file in TomEE. In that case we don't boot the CDI container. But the JSF Container calls CDI.current(). > How should CDI.current() behave in that case? Throwing an IllegalStateException, returning null or return a non-functional BeanManager? > We should also define the behaviour of CDI.getBeanManager while we are at it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (CDI-626) How should CDI.current() and CDI.getBeanManager() behave for non-CDI apps?

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-626?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-626: ------------------------------------- Fix Version/s: 2.0 (discussion) > How should CDI.current() and CDI.getBeanManager() behave for non-CDI apps? > -------------------------------------------------------------------------- > > Key: CDI-626 > URL: https://issues.jboss.org/browse/CDI-626 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Mark Struberg > Labels: F2F2016 > Fix For: 2.0 (discussion) > > > We did hit the following situation: > A user installs a Spring application WAR file in TomEE. In that case we don't boot the CDI container. But the JSF Container calls CDI.current(). > How should CDI.current() behave in that case? Throwing an IllegalStateException, returning null or return a non-functional BeanManager? > We should also define the behaviour of CDI.getBeanManager while we are at it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (CDI-233) Specify target bean archive for bean added via AfterBeanDiscovery.addBean()

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-233?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-233: ------------------------------------- Fix Version/s: 2.0 (discussion) (was: TBD) > Specify target bean archive for bean added via AfterBeanDiscovery.addBean() > --------------------------------------------------------------------------- > > Key: CDI-233 > URL: https://issues.jboss.org/browse/CDI-233 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Portable Extensions > Reporter: Martin Kouba > Labels: F2F2016, visibility > Fix For: 2.0 (discussion) > > > This may have impact, provided that alternatives, interceptors or decorators are used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (CDI-233) Specify target bean archive for bean added via AfterBeanDiscovery.addBean()

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-233?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-233: ------------------------------------- Labels: F2F2016 visibility (was: visibility) > Specify target bean archive for bean added via AfterBeanDiscovery.addBean() > --------------------------------------------------------------------------- > > Key: CDI-233 > URL: https://issues.jboss.org/browse/CDI-233 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Portable Extensions > Reporter: Martin Kouba > Labels: F2F2016, visibility > Fix For: 2.0 (discussion) > > > This may have impact, provided that alternatives, interceptors or decorators are used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev August 2016