[cdi-dev] [JBoss JIRA] (CDI-517) assignability to parameterized required type

[ https://issues.jboss.org/browse/CDI-517?page=com.atlassian.jira.plugin.sy... ] Martin Kouba commented on CDI-517: ---------------------------------- Well, it was added in this commit [42f5f8ec974e24dfdca5c34eadd3f85785077ca5|https://github.com/cdi-spec/cdi/...] (authored on 25 Feb 2013), the Proposed Final Draft was published on *06 Mar, 2013*, and the Final Release was on *24 May, 2013*. That's enough time for revision. It was also discussed in [DELTASPIKE-295|https://issues.apache.org/jira/browse/DELTASPIKE-295]. So I don't understand your "2 days" sentence. In any case, it is incompatible in the sense that it *was not defined in CDI 1.0*. And in my opinion it was a mistake. Also note that it's very easy to fix (and follow the rules explicitly defined in the CDI spec): http://grepcode.com/file/repo1.maven.org/maven2/org.apache.deltaspike.mod... Honestly Mark, do you think it's correct to allow something like this? {code:java} class Foo<T> { private T ref; public Foo(T ref) { this.ref = ref; } } @Produces Foo createFoo() { Foo<Integer> foo = new Foo<Integer>(10); return foo; } // The producer would be assignable... @Inject Foo<String> stringFoo; {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)