December 2013 - cdi-dev - Jboss List Archives

[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 commented on CDI-318: ---------------------------------- Actually this is not a real issue but rather a hint for clarification. An example: {code} @Target({ TYPE, METHOD, PARAMETER, FIELD, CONSTRUCTOR }) @Retention(RUNTIME) @Inherited public @interface Marker { } @Marker public interface Foo { } public class Bar implements Foo { } {code} and observer: {code} public void observeMarker(@WithAnnotations({ Marker.class }) @Observes ProcessAnnotatedType<?> pat) { } {code} I think PAT for Bar should be observed because @Marker is inherited (CDI follows JSL rules here). The question is whether this makes sense because "A bean may inherit type-level metadata and members from its superclasses", not superinterfaces. > @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 > Priority: Minor > Labels: cdi-1.1-mr > > 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

11 years

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 updated CDI-318: ----------------------------- Priority: Minor (was: Major) > @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 > Priority: Minor > Labels: cdi-1.1-mr > > 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

11 years

1
0
0 / 0

[JBoss JIRA] (CDI-379) Clarify life cycle of RequestScoped

by Bill Shannon (JIRA)

[ https://issues.jboss.org/browse/CDI-379?page=com.atlassian.jira.plugin.sy... ] Bill Shannon commented on CDI-379: ---------------------------------- There's two parts to this: 1. The existing uses of @RequestScoped need to be better specified. Yes, that should probably be done in each spec that controls the scope, but until that can be done it would be helpful to do it in the CDI spec. 2. The definition of @RequestScoped needs to be generalized so that it's clear that other specs *can* define their own use of @RequestScoped, and that the use of @RequestScoped isn't limited to the cases currently defined by the CDI spec. > Clarify life cycle of RequestScoped > ----------------------------------- > > Key: CDI-379 > URL: https://issues.jboss.org/browse/CDI-379 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Joseph Snyder > Priority: Minor > > This is one of the areas where the CDI spec could be clearer. It defines > the points where "some" request scope is active, and where "some" request > scope is destroyed, but it doesn't clearly state what the span of a particular > request context is. You sort of have to work backwards and figure it out. > Update the spec to indicate when a particular request scope is > created, what operations it's active during, and when it's destroyed. -- 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

11 years

1
0
0 / 0

Monday EG meeting agenda

by Antoine Sabot-Durand

Dear all, The following issue are the last one to deal with for 1.2 MR inclusion : CDI-380 Clarify SessionScoped CDI-372 clarify behaviour of implicit bean archive CDI-370 Expand @RequestScoped and @SessionScoped to account for WebSocket CDI-320 Clarify whether ProcessAnnotatedType should be fired for annotations CDI-318 @WithAnnotations types can appear on any supertype CDI-280 clarify usage of 'bean' term usage in the spec CDI-220 behaviour of CDI bean @Specializes session bean is undefined I also wanted to have a definitive decision for "CDI -377 automatic JSR-330 annotation processing problematic" We agreed on the fact that specific exclusion list should be maintain at implementation level, but we didn’t decide if the exclusion mechanism (that would allow user to add their own excluded Beanarchive / package) should be exposed in the spec and thus be fixed in 1.2. Which would be great IMHO. Antoine

11 years

1
0
0 / 0

[JBoss JIRA] (CDI-77) Clarify what happens when the user creates a unbound recursive injection with Dependent scoped beans

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-77?page=com.atlassian.jira.plugin.sys... ] Antoine Sabot-Durand closed CDI-77. ----------------------------------- Resolution: Rejected This task was examined during 12/02/2013 EG meeting (Hangout). The specification already specify that container doesn't have to support circular chains of dependencies on pseudo-scope's only beans (Last sentence of Chapter 5 introduction). So this issue is already answered. The answer is "unpredictable result since container doesn't have to support this kind of circular dep" > Clarify what happens when the user creates a unbound recursive injection with Dependent scoped beans > ---------------------------------------------------------------------------------------------------- > > Key: CDI-77 > URL: https://issues.jboss.org/browse/CDI-77 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Resolution > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: TBD > > > for example > class Foo { > @Inject Bar bar; > } > class bar { > @Inject Foo foo; > } -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (CDI-77) Clarify what happens when the user creates a unbound recursive injection with Dependent scoped beans

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-77?page=com.atlassian.jira.plugin.sys... ] Antoine Sabot-Durand updated CDI-77: ------------------------------------ Labels: (was: 12-02-13-EGM cdi-1.1-mr) > Clarify what happens when the user creates a unbound recursive injection with Dependent scoped beans > ---------------------------------------------------------------------------------------------------- > > Key: CDI-77 > URL: https://issues.jboss.org/browse/CDI-77 > Project: CDI Specification Issues > Issue Type: Clarification > Components: Resolution > Affects Versions: 1.0 > Reporter: Pete Muir > Assignee: Pete Muir > Fix For: TBD > > > for example > class Foo { > @Inject Bar bar; > } > class bar { > @Inject Foo foo; > } -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (CDI-379) Clarify life cycle of RequestScoped

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-379?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand closed CDI-379. ------------------------------------ Resolution: Rejected This task was examined during 12/02/2013 EG meeting (Hangout). CDI spec cannot tell how other spec use built-in scopes. So it's the work of each specification to give information about validity and activation of @RequestScoped and others. > Clarify life cycle of RequestScoped > ----------------------------------- > > Key: CDI-379 > URL: https://issues.jboss.org/browse/CDI-379 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Joseph Snyder > Priority: Minor > > This is one of the areas where the CDI spec could be clearer. It defines > the points where "some" request scope is active, and where "some" request > scope is destroyed, but it doesn't clearly state what the span of a particular > request context is. You sort of have to work backwards and figure it out. > Update the spec to indicate when a particular request scope is > created, what operations it's active during, and when it's destroyed. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (CDI-379) Clarify life cycle of RequestScoped

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-379?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-379: ------------------------------------- Labels: (was: 12-02-13-EGM cdi-1.1-mr) > Clarify life cycle of RequestScoped > ----------------------------------- > > Key: CDI-379 > URL: https://issues.jboss.org/browse/CDI-379 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Joseph Snyder > Priority: Minor > > This is one of the areas where the CDI spec could be clearer. It defines > the points where "some" request scope is active, and where "some" request > scope is destroyed, but it doesn't clearly state what the span of a particular > request context is. You sort of have to work backwards and figure it out. > Update the spec to indicate when a particular request scope is > created, what operations it's active during, and when it's destroyed. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (CDI-412) Add assertions to tests located in org.jboss.cdi.tck.interceptors.tests.aroundConstruct package and subpackages

by Martin Kouba (JIRA)

Martin Kouba created CDI-412: -------------------------------- Summary: Add assertions to tests located in org.jboss.cdi.tck.interceptors.tests.aroundConstruct package and subpackages Key: CDI-412 URL: https://issues.jboss.org/browse/CDI-412 Project: CDI Specification Issues Issue Type: Feature Request Components: Interceptors Reporter: Martin Kouba These tests do not contain assertions because it wasn't clear whether the Interceptors 1.2 spec will have its own TCK. -- 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

11 years

1
0
0 / 0

Google short URL

by Antoine Sabot-Durand

Hi, Just to let you know that thanks to website association Google allowed us to create a short URL for CDI G+ page : google.com/+CdiSpecOrgPage. The drawback is that we lost most of our +1 in the process (we add +105 and reverted +29) probably due to the score of official website page. Antoine

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev December 2013