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

[Martin Kouba (JIRA)]

    [ https://issues.jboss.org/browse/CDI-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13048471#comment-13048471 ] 

Martin Kouba commented on CDI-517:
----------------------------------

bq. It's at least fine from a pure Java aspect
Works but it's not recommended and you get a compiler warning.
bq. Also note that returning a ParameterizedType does NOT work in the EE6 RI, nor in WebSphere and also not in older JBossAS versions.
I don't understand. There is a TCK test (since 1.0.x) for a producer method which returns a parameterized type: [ProducerMethodDefinitionTest#testParameterizedReturnType()|https://github.com/cdi-spec/cdi-tck/blob/1.0/impl/src/main/java/org/jboss/jsr299/tck/tests/implementation/producer/method/definition/ProducerMethodDefinitionTest.java#L84].

> 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)