[jira] [Commented] (ARIES-1607) Blueprint injection checking goes far beyond OSGi spec

["Jean-Philippe CLEMENT (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARIES-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15470021#comment-15470021 ] 

Jean-Philippe CLEMENT commented on ARIES-1607:
----------------------------------------------

Follows initial ARIES-1500 request on generics - as per Guillaume "I think our implementation goes way beyond what the OSGi spec says. I think if we want to go beyond, i.e. allow non enforceable casts, we need a flag somewhere to turn on this feature. If you want to provide a patch to go that way, please open a new jira."

> Blueprint injection checking goes far beyond OSGi spec
> ------------------------------------------------------
>
>                 Key: ARIES-1607
>                 URL: https://issues.apache.org/jira/browse/ARIES-1607
>             Project: Aries
>          Issue Type: Bug
>    Affects Versions: blueprint-core-1.6.2
>            Reporter: Jean-Philippe CLEMENT
>            Priority: Critical
>
> Blueprint should only inject objects depending on their class the way the JVM works at runtime.
> At runtime there is no difference between:
>  List getSomething();
> and
>  List<String> getSomething();
> Furthermore Java prevents having both methods above declared in the same class. Same if List were List<Object>. A list is a list no matter the generic type.
> The generic type checking is made at compilation time. Blueprint is not a compiler :)
> Please at least add a flag to enforce or not the generic type checking!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)