January 2014 - cdi-dev - Jboss List Archives

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-389?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand reassigned CDI-389: ---------------------------------------- Assignee: Antoine Sabot-Durand > Revert CDI-85 > ------------- > > Key: CDI-389 > URL: https://issues.jboss.org/browse/CDI-389 > Project: CDI Specification Issues > Issue Type: Bug > Affects Versions: 1.1.PFD > Reporter: Marko Lukša > Assignee: Antoine Sabot-Durand > Labels: CDI_spec_chge, Ready_to_fix > Fix For: 1.2 Proposed > > > Bullet 4 of section 5.2.4 should be reverted back from: > {quote} > the required type parameter is an actual type, the bean type parameter is a type variable and the actual type is assignable *from* > the upper bound, if any, of the type variable, or > {quote} > to > {quote} > the required type parameter is an actual type, the bean type parameter is a type variable and the actual type is assignable *to* > the upper bound, if any, of the type variable, or > {quote} > See discussion at http://lists.jboss.org/pipermail/cdi-dev/2013-July/004290.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-318) @WithAnnotations types can appear on any supertype

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-318?page=com.atlassian.jira.plugin.sy... ] Martin Kouba reassigned CDI-318: -------------------------------- Assignee: Martin Kouba > @WithAnnotations types can appear on any supertype > -------------------------------------------------- > > Key: CDI-318 > URL: https://issues.jboss.org/browse/CDI-318 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Martin Kouba > Assignee: Martin Kouba > Priority: Minor > Labels: CDI_api_chge, Ready_to_fix > Fix For: 1.2 Proposed > > > Is this intentional? Supertypes also include interfaces which are not very useful here as beans may inherit type-level metadata and members from superclasses only. > Is there any special use-case for this? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-382) Clarify interceptors are not associated with the result of a producer method/field

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-382?page=com.atlassian.jira.plugin.sy... ] Martin Kouba reassigned CDI-382: -------------------------------- Assignee: Martin Kouba > Clarify interceptors are not associated with the result of a producer method/field > ---------------------------------------------------------------------------------- > > Key: CDI-382 > URL: https://issues.jboss.org/browse/CDI-382 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Interceptors > Affects Versions: 1.1.PFD > Reporter: Martin Kouba > Assignee: Martin Kouba > Labels: CDI_spec_chge, Ready_to_fix > Fix For: 1.2 Proposed > > > The interceptors part from CDI-59 resolution [1] is missing in the final version of the spec, probably lost during the Interceptors section transfer to the Interceptors 1.2 spec. > [1] https://github.com/cdi-spec/cdi/pull/110 > "Interceptors are not associated with the return value of a producer method or the current value of a producer field." -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-416) Typo for @PersistencContext at section 7.3.6

by Michel Graciano (JIRA)

[ https://issues.jboss.org/browse/CDI-416?page=com.atlassian.jira.plugin.sy... ] Michel Graciano updated CDI-416: -------------------------------- Description: At section 7.3.6 [1] there is a typo for @PersistencContext where it should be @PersistenceContext. [1] http://docs.jboss.org/cdi/spec/1.1/cdi-spec.html#resource_lifecycle was: At section 7.3.6 [1] there is a type for @PersistencContext where it should be @PersistenceContext. [1] http://docs.jboss.org/cdi/spec/1.1/cdi-spec.html#resource_lifecycle > Typo for @PersistencContext at section 7.3.6 > -------------------------------------------- > > Key: CDI-416 > URL: https://issues.jboss.org/browse/CDI-416 > Project: CDI Specification Issues > Issue Type: Bug > Affects Versions: 1.1.PFD > Reporter: Michel Graciano > Priority: Minor > > At section 7.3.6 [1] there is a typo for @PersistencContext where it should be @PersistenceContext. > [1] http://docs.jboss.org/cdi/spec/1.1/cdi-spec.html#resource_lifecycle -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-416) Typo for @PersistencContext at section 7.3.6

by Michel Graciano (JIRA)

Michel Graciano created CDI-416: ----------------------------------- Summary: Typo for @PersistencContext at section 7.3.6 Key: CDI-416 URL: https://issues.jboss.org/browse/CDI-416 Project: CDI Specification Issues Issue Type: Bug Affects Versions: 1.1.PFD Reporter: Michel Graciano Priority: Minor At section 7.3.6 [1] there is a type for @PersistencContext where it should be @PersistenceContext. [1] http://docs.jboss.org/cdi/spec/1.1/cdi-spec.html#resource_lifecycle -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

CDI 1.2 Implementation

by Jozef Hartinger

Hi all, as many of you know already, Weld 2.2 is going to be the reference implementation of the upcoming maintenance release of the CDI specification. CDI is an EE specification. That implies that the CDI TCK which validates a CDI implementation has to be run against an EE container not just the CDI implementation itself (e.g. Weld Core). So far, both existing releases of CDI (1.0 and 1.1) were always part of a major Java EE release (6 and 7). It therefore made sense to require the CDI RI to run as part of the GlassFish application server since GlassFish is the RI for each recent Java EE version. However, with CDI 1.2 the situation is different. Since CDI 1.2 is not part of a major Java EE release, we see no reason to require the CDI 1.2 RI to run specifically on GlassFish at the end of the maintenance release window. Instead, any Java EE 7 certified application server should be suitable. Therefore, we are going to use WildFly (http://wildfly.org/) as the runtime for CDI 1.2 RI and TCK. Note that this by no means defines which Java EE servers will or will not support CDI 1.2. This proposal only defines which Java EE server will be used at the end of the CDI 1.2 MR effort to validate the RI and the TCK. Regards, Jozef

10 years, 2 months

3
7
0 / 0

[JBoss JIRA] (CDI-404) adding bean-defining annotations for Interceptor while setting bean-discovery-mode="annotated"

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/CDI-404?page=com.atlassian.jira.plugin.sy... ] Pete Muir commented on CDI-404: ------------------------------- +1 for Option 1 > adding bean-defining annotations for Interceptor while setting bean-discovery-mode="annotated" > ----------------------------------------------------------------------------------------------- > > Key: CDI-404 > URL: https://issues.jboss.org/browse/CDI-404 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Beans > Affects Versions: 1.1.PFD > Reporter: Tang Yong > Labels: CDI_spec_chge, CDI_tck_chge > Fix For: 1.2 Proposed > > > [1] and [2] has reported an issue about > bean-discovery-mode="annotated". Although there are some workarounds for > the issue, I think that in the future, we should support interceptor > implict scanning while an user uses bean-discovery-mode="annotated". > Apparently, just as bean-discovery-mode="annotated", CDI Spec and > Interceptor Spec are disconnected. > [1]:https://java.net/jira/browse/GLASSFISH-20667 > [2]:http://stackoverflow.com/questions/17258639/interceptor-issue-with-jav... > About detailed discussion, please seeing the following, > https://java.net/projects/javaee-spec/lists/users/archive/2013-09/message/7 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-398) Clarify that an array with a variable component type or parameterized component type containing wildcards is not a valid bean type

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-398?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand edited comment on CDI-398 at 1/28/14 5:22 AM: ------------------------------------------------------------------- Done [~jharting], but don't be shy : you're the TCK specialist here ;). was (Author: antoinesabot-durand): Done [~jharting], but don't be shy : you're the TCK specialist her ;). > Clarify that an array with a variable component type or parameterized component type containing wildcards is not a valid bean type > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: CDI-398 > URL: https://issues.jboss.org/browse/CDI-398 > Project: CDI Specification Issues > Issue Type: Bug > Components: Beans > Affects Versions: 1.1.PFD > Reporter: Marko Lukša > Labels: CDI_spec_chge, CDI_tck_chge, Ready_to_fix > Fix For: 1.2 Proposed > > > Section 2.2.1 says: > {quote} > Almost any Java type may be a bean type of a bean: > • A bean type may be an array type. > {quote} > and: > {quote} > A type variable is not a legal bean type. A parameterized type that contains a wildcard type parameter is not a legal bean type. > {quote} > This should be clarified that array types that have a type variable or a parameterized type that contains a wildcard type parameter as the array's component type are also not legal bean types. > Also, all other sections that mention type variables/wildcards should also be reviewed and, if necessary, updated to also specifically mention array types with these kinds of component types. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-398) Clarify that an array with a variable component type or parameterized component type containing wildcards is not a valid bean type

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-398?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand commented on CDI-398: ------------------------------------------ Done [~jharting], but don't be shy : you're the TCK specialist her ;). > Clarify that an array with a variable component type or parameterized component type containing wildcards is not a valid bean type > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: CDI-398 > URL: https://issues.jboss.org/browse/CDI-398 > Project: CDI Specification Issues > Issue Type: Bug > Components: Beans > Affects Versions: 1.1.PFD > Reporter: Marko Lukša > Labels: CDI_spec_chge, CDI_tck_chge, Ready_to_fix > Fix For: 1.2 Proposed > > > Section 2.2.1 says: > {quote} > Almost any Java type may be a bean type of a bean: > • A bean type may be an array type. > {quote} > and: > {quote} > A type variable is not a legal bean type. A parameterized type that contains a wildcard type parameter is not a legal bean type. > {quote} > This should be clarified that array types that have a type variable or a parameterized type that contains a wildcard type parameter as the array's component type are also not legal bean types. > Also, all other sections that mention type variables/wildcards should also be reviewed and, if necessary, updated to also specifically mention array types with these kinds of component types. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (CDI-398) Clarify that an array with a variable component type or parameterized component type containing wildcards is not a valid bean type

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-398?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-398: ------------------------------------- Labels: CDI_spec_chge CDI_tck_chge Ready_to_fix (was: CDI_spec_chge Ready_to_fix) > Clarify that an array with a variable component type or parameterized component type containing wildcards is not a valid bean type > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: CDI-398 > URL: https://issues.jboss.org/browse/CDI-398 > Project: CDI Specification Issues > Issue Type: Bug > Components: Beans > Affects Versions: 1.1.PFD > Reporter: Marko Lukša > Labels: CDI_spec_chge, CDI_tck_chge, Ready_to_fix > Fix For: 1.2 Proposed > > > Section 2.2.1 says: > {quote} > Almost any Java type may be a bean type of a bean: > • A bean type may be an array type. > {quote} > and: > {quote} > A type variable is not a legal bean type. A parameterized type that contains a wildcard type parameter is not a legal bean type. > {quote} > This should be clarified that array types that have a type variable or a parameterized type that contains a wildcard type parameter as the array's component type are also not legal bean types. > Also, all other sections that mention type variables/wildcards should also be reviewed and, if necessary, updated to also specifically mention array types with these kinds of component types. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev January 2014