Just for people who will read this thread later complete Qux class is:<div><br></div><div><pre style="word-wrap:break-word;white-space:pre-wrap">public class Qux extends Baz<String> {
public Qux(String name) {
}
}</pre><pre style="word-wrap:break-word;white-space:pre-wrap"><br></pre><div><div><i>Romain Manni-Bucau</i></div><div><i>Twitter: <a href="https://twitter.com/rmannibucau" target="_blank">@rmannibucau</a></i></div><div><i>Blog: </i><a href="http://rmannibucau.wordpress.com/" target="_blank"><i>http://rmannibucau.wordpress.com/</i></a></div>
<div><i>LinkedIn: </i><font color="#0000ee"><i><u><a href="http://fr.linkedin.com/in/rmannibucau" target="_blank">http://fr.linkedin.com/in/rmannibucau</a></u></i></font></div><div><i><span style="background-color:rgb(255,255,255)">Github: </span><a href="https://github.com/rmannibucau" target="_blank">https://github.com/rmannibucau</a></i></div>
<div><br></div></div>
<br><br><div class="gmail_quote">2013/7/8 Martin Kouba <span dir="ltr"><<a href="mailto:mkouba@redhat.com" target="_blank">mkouba@redhat.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Re Arne's question:<br>
Yes, Baz is a managed bean and AmbiguousResolutionException should not<br>
be thrown because Qux is not a managed bean (doesn't have a public<br>
no-arg constructor).<br>
<br>
Re Marko's findings:<br>
Yes, the TCK assertions are not up to date and Baz<T> is not assignable<br>
to Baz<String>, because String is not assignable from Object (no bound<br>
is defined -> Object is assumed; see JSL 4.4). So I confirm a TCK issue.<br>
<br>
IMO this would deserve a proper cleanup...<br>
<br>
Martin<br>
<br>
Dne 8.7.2013 01:22, Marko Lukša napsal(a):<br>
<div class="HOEnZb"><div class="h5">> I'd say it's a bug. While Baz indeed is a managed bean, it shouldn't be<br>
> injected into injection point with type Baz<String> nor Baz<List<Qux>>.<br>
> So I believe you're right in saying that this test should fail with<br>
> UnsatisfiedResolutionException.<br>
><br>
> There was a change made to the spec way back in 2010 (see [1]), but the<br>
> TCK apparently wasn't updated then. I've filed an issue in the TCK jira<br>
> [2].<br>
><br>
> The problem isn't only in the TCK, but also in the spec itself. Some of<br>
> the examples in section 5.2.4 don't conform to the rules defined in the<br>
> same section (according to the rules, bean Dao<T extends Persistent><br>
> shouldn't be eligible for injection into Dao<Order> or Dao<User>). I<br>
> remember asking about this a year ago ([3]), but I didn't articulate the<br>
> problem properly.<br>
><br>
> [1]<br>
> <a href="https://github.com/cdi-spec/cdi/commit/b32243350ace6a0bba337f91a35f5fd05c151f14" target="_blank">https://github.com/cdi-spec/cdi/commit/b32243350ace6a0bba337f91a35f5fd05c151f14</a><br>
> [2] <a href="https://issues.jboss.org/browse/CDITCK-349" target="_blank">https://issues.jboss.org/browse/CDITCK-349</a><br>
> [3] <a href="http://lists.jboss.org/pipermail/cdi-dev/2012-April/001742.html" target="_blank">http://lists.jboss.org/pipermail/cdi-dev/2012-April/001742.html</a><br>
><br>
> Marko<br>
><br>
> On 7.7.2013 16:04, Arne Limburg wrote:<br>
>> Hi all,<br>
>><br>
>> At the OpenWebBeans list we are currently discussing handling of<br>
>> generics in CDI.<br>
>> I found a test in the CDI 1.1 TCK, which imho has a bug. The test<br>
>> is org.jboss.cdi.tck.tests.inheritance.generics.MemberLevelInheritanceTest<br>
>> and the (simplified) deployment scenario is the following:<br>
>><br>
>> public class Baz<T> {<br>
>> }<br>
>><br>
>> public class Qux extends Baz<String> {<br>
>> }<br>
>><br>
>> @Vetoed<br>
>> public class Bar<T1, T2> {<br>
>> @Inject<br>
>> private Baz<T1> baz;<br>
>> @Inject<br>
>> private Baz<List<T2>> t2BazList;<br>
>> }<br>
>><br>
>> @RequestScoped<br>
>> public class Foo extends Bar<String, Qux> {<br>
>> }<br>
>><br>
>> public class Producer {<br>
>> @Produces<br>
>> @Amazing<br>
>> public String produceString() {<br>
>> return "ok";<br>
>> }<br>
>><br>
>> @Produces<br>
>> public String[] produceStringArray() {<br>
>> return new String[0];<br>
>> }<br>
>><br>
>> @Produces<br>
>> public Baz<Baz<Qux>> produceBazBazQux() {<br>
>> return new Baz();<br>
>> }<br>
>> }<br>
>><br>
>> The class Bar has some more injection points, but that does not matter.<br>
>> Due to the TCK this deployment should work, but I don't know how.<br>
>> Question: Is Baz a Bean (I suppose so) and may it be injected into<br>
>> Bean Foo, more precisely into the second injection point of class Bar?<br>
>> - If yes, it also should be injected into the first injection<br>
>> point, right? This would lead to an AmbiguousResolutionException since<br>
>> Qux may also be injected into the first injection point.<br>
>> - If no, the deployment should fail with a<br>
>> UnsatisfiedResolutionException since there is no Bean that can be<br>
>> injected into that injection point.<br>
>><br>
>> Is this a bug in the TCK and if not, how is this supposed to work?<br>
>><br>
>> Cheers,<br>
>> Arne<br>
>><br>
>><br>
>> _______________________________________________<br>
>> cdi-dev mailing list<br>
>> <a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> cdi-dev mailing list<br>
> <a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
><br>
_______________________________________________<br>
cdi-dev mailing list<br>
<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
</div></div></blockquote></div><br></div>