November 2016 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-461) Configuration Epic for CDI 2.0

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-461?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand closed CDI-461. ------------------------------------ Resolution: Done > Configuration Epic for CDI 2.0 > ------------------------------ > > Key: CDI-461 > URL: https://issues.jboss.org/browse/CDI-461 > Project: CDI Specification Issues > Issue Type: Epic > Reporter: Antoine Sabot-Durand > Fix For: 2.0 .Final > > > This Epic ticket gathers all tickets and work document about studying the possible introduction of configuration feature in CDI 2.0. > Draft document is here : https://docs.google.com/document/d/1378aTRNgCMXRYP9LBYRuGdan0mmQ3rPjjIYLW... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-461) Configuration Epic for CDI 2.0

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-461?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-461: ------------------------------------- Fix Version/s: 2.0 .Final (was: 2.0 (discussion)) > Configuration Epic for CDI 2.0 > ------------------------------ > > Key: CDI-461 > URL: https://issues.jboss.org/browse/CDI-461 > Project: CDI Specification Issues > Issue Type: Epic > Reporter: Antoine Sabot-Durand > Fix For: 2.0 .Final > > > This Epic ticket gathers all tickets and work document about studying the possible introduction of configuration feature in CDI 2.0. > Draft document is here : https://docs.google.com/document/d/1378aTRNgCMXRYP9LBYRuGdan0mmQ3rPjjIYLW... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-462) Parts Epic for CDI 2.0

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-462?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand closed CDI-462. ------------------------------------ > Parts Epic for CDI 2.0 > ---------------------- > > Key: CDI-462 > URL: https://issues.jboss.org/browse/CDI-462 > Project: CDI Specification Issues > Issue Type: Epic > Reporter: Antoine Sabot-Durand > Fix For: 2.0 .Final > > > this Epic ticket gathers all tickets and work documents about the introudction of parts (modularity) in CDI 2.0 > Draft document is here : https://docs.google.com/document/d/1AEBjQl00CZ9ERfgXSHq9cdxrngwsERjUCEmcd... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-462) Parts Epic for CDI 2.0

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-462?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-462: ------------------------------------- Fix Version/s: 2.0 .Final (was: 2.0 (discussion)) > Parts Epic for CDI 2.0 > ---------------------- > > Key: CDI-462 > URL: https://issues.jboss.org/browse/CDI-462 > Project: CDI Specification Issues > Issue Type: Epic > Reporter: Antoine Sabot-Durand > Fix For: 2.0 .Final > > > this Epic ticket gathers all tickets and work documents about the introudction of parts (modularity) in CDI 2.0 > Draft document is here : https://docs.google.com/document/d/1AEBjQl00CZ9ERfgXSHq9cdxrngwsERjUCEmcd... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-462) Parts Epic for CDI 2.0

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-462?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand resolved CDI-462. -------------------------------------- Resolution: Rejected > Parts Epic for CDI 2.0 > ---------------------- > > Key: CDI-462 > URL: https://issues.jboss.org/browse/CDI-462 > Project: CDI Specification Issues > Issue Type: Epic > Reporter: Antoine Sabot-Durand > Fix For: 2.0 .Final > > > this Epic ticket gathers all tickets and work documents about the introudction of parts (modularity) in CDI 2.0 > Draft document is here : https://docs.google.com/document/d/1AEBjQl00CZ9ERfgXSHq9cdxrngwsERjUCEmcd... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-462) Parts Epic for CDI 2.0

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-462?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand reopened CDI-462: -------------------------------------- > Parts Epic for CDI 2.0 > ---------------------- > > Key: CDI-462 > URL: https://issues.jboss.org/browse/CDI-462 > Project: CDI Specification Issues > Issue Type: Epic > Reporter: Antoine Sabot-Durand > Fix For: 2.0 .Final > > > this Epic ticket gathers all tickets and work documents about the introudction of parts (modularity) in CDI 2.0 > Draft document is here : https://docs.google.com/document/d/1AEBjQl00CZ9ERfgXSHq9cdxrngwsERjUCEmcd... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-630) Revise javax.enterprise.util.AnnotationLiteral.cachedHashCode

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-630?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand resolved CDI-630. -------------------------------------- Fix Version/s: (was: 2.0 (discussion)) Resolution: Won't Fix > Revise javax.enterprise.util.AnnotationLiteral.cachedHashCode > ------------------------------------------------------------- > > Key: CDI-630 > URL: https://issues.jboss.org/browse/CDI-630 > Project: CDI Specification Issues > Issue Type: Feature Request > Reporter: Martin Kouba > Priority: Optional > > Currently, {{AnnotationLiteral.hashCode()}} always returns {{0}} if there are no members (ignoring annotation type completely). Although it does not break {{Object.hashCode()}} contract, I believe we should -either return a number based on the annotation type (to make the annotation literal instances more usable in hash tables) or- simply return zero and don't cache the value at all. > UPDATE: We may not return a number based on the annotation type because it would break the {{java.lang.annotation.Annotation.hashCode()}} contract. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-631) Improve AnnotationLiteral for empty annotations

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-631?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-631: ------------------------------------- Fix Version/s: 2.1 (Discussion) (was: 2.0 (discussion)) > Improve AnnotationLiteral for empty annotations > ----------------------------------------------- > > Key: CDI-631 > URL: https://issues.jboss.org/browse/CDI-631 > Project: CDI Specification Issues > Issue Type: Feature Request > Reporter: Mark Struberg > Fix For: 2.1 (Discussion) > > > Annotation hashCode() and equals() operations are fairly expensive as they always invoke getDeclaredMethods() even if there are no such. And getDeclaredMethods involves the SecurityManager + wrapper classes + Exception handling + + + > That's horrible expensive. > In OWB I improved this by introducing an own base class for dynamic annotations which do not have any members: > https://github.com/apache/openwebbeans/blob/trunk/webbeans-impl/src/main/... > The method returns a hardcoded String for toString(), returns hardcoded 0 as hashCode and the equals() method invokes the equals on the annotation type. > We might support this improvements directly in the AnnotationLiteral class or introduce a similar 2nd class especially for empty annotations? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-629) Consider standardizing AnnotationInstaceProvider from DeltaSpike

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-629?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-629: ------------------------------------- Fix Version/s: 2.1 (Discussion) (was: 2.0 (discussion)) > Consider standardizing AnnotationInstaceProvider from DeltaSpike > ---------------------------------------------------------------- > > Key: CDI-629 > URL: https://issues.jboss.org/browse/CDI-629 > Project: CDI Specification Issues > Issue Type: Feature Request > Reporter: Martin Kouba > Fix For: 2.1 (Discussion) > > > http://lists.jboss.org/pipermail/cdi-dev/2016-September/008829.html > Impl. notes: > * the type safety is not guaranteed in the current version of > {{AnnotationInstanceProvider}} (deltaspike) > * {{AnnotationInstanceProvider}} implements {{Serializable}} but a user is allowed to provide a map instance which is not serializable or contains values which are not serializable > * the provided map of values should be copied (it can be mutable) > * we should at least check the provided map of member values against the set of declared methods -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (CDI-502) Clarify "contains" meaning in "Legal bean types" specification.

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-502?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-502: ------------------------------------- Fix Version/s: 2.1 (Discussion) (was: 2.0 (discussion)) > Clarify "contains" meaning in "Legal bean types" specification. > --------------------------------------------------------------- > > Key: CDI-502 > URL: https://issues.jboss.org/browse/CDI-502 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Beans, Inheritance and Specialization > Reporter: Tomasz Krakowiak > Assignee: Antoine Sabot-Durand > Fix For: 2.1 (Discussion) > > > CDI 1.1, section 2.2.1. Legal bean types says: > {quote} > A parameterized type that contains a wildcard type parameter is not a legal bean type. > {quote} > Does it means direct containment or deep/recursive containment? > I understand this is clearly illegal: > {code} > @Produces > List<?> produceList(){ > //... > } > {code} > But, are those two bean definitions legal: > {code} > @Produces > List<Optional<?>> produceList(){ > //... > } > {code} > {code} > // Bean types: MyList, List<Optional<?>>, Object > // or > // Bean types: MyList, Object > @Dependent > MyList extends List<Optional<?>> { > //... > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 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 2016