[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:
----------------------------------
bq. Check out my sample app. It runs fine on Weld-1.1.23.Final but is broken in Weld-2.
This is expected.
bq. If there would be a working CDI-1.0 TCK test this would mean that Weld-1 does not pass
the TCK.
Could you be more specific? What does it mean _"returning a ParameterizedType does
NOT work in the EE6 RI"_? There is no test for assignability of a raw return type to
a parameterized required type. But there's a test for assignability of a parameterized
return type to a parameterized required type.
assignability to parameterized required type
--------------------------------------------
Key: CDI-517
URL: https://issues.jboss.org/browse/CDI-517
Project: CDI Specification Issues
Issue Type: Bug
Components: Resolution
Affects Versions: 1.1.PFD, 1.2.Final
Reporter: Mark Struberg
2 days before the CDI-1.1 spec went PDF the following backward-incomatible change was
made:
{quote}
-A raw bean type is considered assignable to a parameterized required type if the raw
types are identical.
+ A raw bean type is considered assignable to a parameterized required type if the raw
types are identical and all type parameters of the bean type are either unbounded type
variables or java.lang.Object.
{quote}
This breaks a lot of projects and also is also not compatible with the JavaEE6 RI and the
CDI-1.0 RI where this was explicitly allowed.
This is a follow up to CDI-304.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)