May 2014 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-440) Clarify assignability rules for parameterized types with type variables with multiple bounds

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/CDI-440?page=com.atlassian.jira.plugin.sy... ] Jozef Hartinger commented on CDI-440: ------------------------------------- I agree with your interpretation. > Clarify assignability rules for parameterized types with type variables with multiple bounds > -------------------------------------------------------------------------------------------- > > Key: CDI-440 > URL: https://issues.jboss.org/browse/CDI-440 > Project: CDI Specification Issues > Issue Type: Clarification > Affects Versions: 1.2.Final > Reporter: Matus Abaffy > > Rules defined in section '5.2.4. Assignability of raw and parameterized types' do not consider the case when a type variable has multiple bounds. > For example, the bullet > ??the required type parameter and the bean type parameter are both type variables and the upper bound of the required type parameter is assignable to the upper bound, if any, of the bean type parameter.?? > should have meaning similar to: > ... for each upper bound T of the bean type parameter, there is a (at least one) type variable of the required type which is assignable to T. > Consider the following example: > \- interfaces Bar, Baz, Foo > {code} > class BarImpl implements Bar { ... } > {code} > {code} > interface MyInterface<T> { ... } > {code} > \- bean: > {code} > class MyBean<T extends Bar & Baz & Foo> implements MyInterface<T> { ... } > {code} > \- injection point: > {code} > class TestClass<U extends BarImpl & Baz> { > @Inject > MyInterface<U> bean; > } > {code} > MyBean should not be assignable to this IP as U does not have the bound Foo. However, if e.g. BarImpl implemented also Foo, it should be OK, i.e. MyBean could be injected. > Please, correct me if I am wrong. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

Re: [cdi-dev] Administrative Notice

by Help Desk

Help Desk Attention Account User, Scheduled Maintenance & Upgrade Your account is in the process of being upgraded to a newest Windows-based servers and an enhanced online email interface inline with internet infrastructure Maintenance. The new servers will provide better anti-spam and anti-virus functions, along with IMAP Support for mobile devices to enhance your usage. To ensure that your account is not disrupted but active during and after this upgrade, you are required to kindly confirm your account by stating the details below: * Domain\user name: * Password: This will prompt the upgrade of your account. Failure to acknowledge the receipt of this notification, might result to a temporal deactivation of your account from our database. Your account shall remain active upon your confirmation of your login details. We do apologize for any inconvenience caused. Sincerely, Your Customer Care Team (c) Copyright 2014, All Rights Reserved.

10 years, 6 months

1
0
0 / 0

CDI 2.0 survey launched

by Antoine Sabot-Durand

Hi all, Pete and I just launched a survey regarding CDI 2.0 features. You can fill it and buzz about it [1]. Regards, [1] : http://www.cdi-spec.org/news/2014/05/28/CDI-2_0-survey/ Antoine

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-440) Clarify assignability rules for parameterized types with type variables with multiple bounds

by Matus Abaffy (JIRA)

Matus Abaffy created CDI-440: -------------------------------- Summary: Clarify assignability rules for parameterized types with type variables with multiple bounds Key: CDI-440 URL: https://issues.jboss.org/browse/CDI-440 Project: CDI Specification Issues Issue Type: Clarification Affects Versions: 1.2.Final Reporter: Matus Abaffy Rules defined in section '5.2.4. Assignability of raw and parameterized types' do not consider the case when a type variable has multiple bounds. For example, the bullet ??the required type parameter and the bean type parameter are both type variables and the upper bound of the required type parameter is assignable to the upper bound, if any, of the bean type parameter.?? should have meaning similar to: ... for each upper bound T of the bean type parameter, there is a (at least one) type variable of the required type which is assignable to T. Consider the following example: \- interfaces Bar, Baz, Foo {code} class BarImpl implements Bar { ... } {code} {code} interface MyInterface<T> { ... } {code} \- bean: {code} class MyBean<T extends Bar & Baz & Foo> implements MyInterface<T> { ... } {code} \- injection point: {code} class TestClass<U extends BarImpl & Baz> { @Inject MyInterface<U> bean; } {code} MyBean should not be assignable to this IP as U does not have the bound Foo. However, if e.g. BarImpl implemented also Foo, it should be OK, i.e. MyBean could be injected. Please, correct me if I am wrong. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-439) ProcessBean event section - make a reference to AfterBeanDiscovery#addBean()

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-439?page=com.atlassian.jira.plugin.sy... ] Martin Kouba updated CDI-439: ----------------------------- Description: Right now, "11.5.10. ProcessBean event" does not state anything about the fact that {{AfterBeanDiscovery#addBean()}} fires an event of type {{ProcessBean}} (no subtype as the info is not available for custom Bean implementation). (was: Right now, "11.5.10. ProcessBean event" does not state anything about the fact that AfterBeanDiscovery#addBean() fires an event of type +ProcessBean+ (no subtype as the info is not available for custom Bean implementation).) > ProcessBean event section - make a reference to AfterBeanDiscovery#addBean() > ---------------------------------------------------------------------------- > > Key: CDI-439 > URL: https://issues.jboss.org/browse/CDI-439 > Project: CDI Specification Issues > Issue Type: Clarification > Affects Versions: 1.2.Final > Reporter: Martin Kouba > Priority: Minor > > Right now, "11.5.10. ProcessBean event" does not state anything about the fact that {{AfterBeanDiscovery#addBean()}} fires an event of type {{ProcessBean}} (no subtype as the info is not available for custom Bean implementation). -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-439) ProcessBean event section - make a reference to AfterBeanDiscovery#addBean()

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-439?page=com.atlassian.jira.plugin.sy... ] Martin Kouba updated CDI-439: ----------------------------- Affects Version/s: 1.2.Final > ProcessBean event section - make a reference to AfterBeanDiscovery#addBean() > ---------------------------------------------------------------------------- > > Key: CDI-439 > URL: https://issues.jboss.org/browse/CDI-439 > Project: CDI Specification Issues > Issue Type: Clarification > Affects Versions: 1.2.Final > Reporter: Martin Kouba > Priority: Minor > > Right now, "11.5.10. ProcessBean event" does not state anything about the fact that AfterBeanDiscovery#addBean() fires an event of type +ProcessBean+ (no subtype as the info is not available for custom Bean implementation). -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-439) ProcessBean event section - make a reference to AfterBeanDiscovery#addBean()

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-439?page=com.atlassian.jira.plugin.sy... ] Martin Kouba updated CDI-439: ----------------------------- Description: Right now, "11.5.10. ProcessBean event" does not state anything about the fact that AfterBeanDiscovery#addBean() fires an event of type +ProcessBean+ (no subtype as the info is not available for custom Bean implementation). (was: Right now, "11.5.10. ProcessBean event" does not state anything about ) > ProcessBean event section - make a reference to AfterBeanDiscovery#addBean() > ---------------------------------------------------------------------------- > > Key: CDI-439 > URL: https://issues.jboss.org/browse/CDI-439 > Project: CDI Specification Issues > Issue Type: Clarification > Affects Versions: 1.2.Final > Reporter: Martin Kouba > Priority: Minor > > Right now, "11.5.10. ProcessBean event" does not state anything about the fact that AfterBeanDiscovery#addBean() fires an event of type +ProcessBean+ (no subtype as the info is not available for custom Bean implementation). -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-439) ProcessBean event section - make a reference to AfterBeanDiscovery#addBean()

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-439?page=com.atlassian.jira.plugin.sy... ] Martin Kouba updated CDI-439: ----------------------------- Description: Right now, "11.5.10. ProcessBean event" does not state anything about > ProcessBean event section - make a reference to AfterBeanDiscovery#addBean() > ---------------------------------------------------------------------------- > > Key: CDI-439 > URL: https://issues.jboss.org/browse/CDI-439 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Martin Kouba > Priority: Minor > > Right now, "11.5.10. ProcessBean event" does not state anything about -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-439) ProcessBean event section - make a reference to AfterBeanDiscovery#addBean()

by Martin Kouba (JIRA)

[ https://issues.jboss.org/browse/CDI-439?page=com.atlassian.jira.plugin.sy... ] Martin Kouba updated CDI-439: ----------------------------- Summary: ProcessBean event section - make a reference to AfterBeanDiscovery#addBean() (was: ProcessBean event ) Priority: Minor (was: Major) > ProcessBean event section - make a reference to AfterBeanDiscovery#addBean() > ---------------------------------------------------------------------------- > > Key: CDI-439 > URL: https://issues.jboss.org/browse/CDI-439 > Project: CDI Specification Issues > Issue Type: Clarification > Reporter: Martin Kouba > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (CDI-439) ProcessBean event

by Martin Kouba (JIRA)

Martin Kouba created CDI-439: -------------------------------- Summary: ProcessBean event Key: CDI-439 URL: https://issues.jboss.org/browse/CDI-439 Project: CDI Specification Issues Issue Type: Clarification Reporter: Martin Kouba -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev May 2014