You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Jean-Philippe CLEMENT (JIRA)" <ji...@apache.org> on 2016/09/07 08:40:20 UTC
[jira] [Updated] (ARIES-1607) Blueprint injection checking goes far
beyond OSGi spec
[ https://issues.apache.org/jira/browse/ARIES-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Philippe CLEMENT updated ARIES-1607:
-----------------------------------------
Description:
Blueprint should only check constuctor and method arguments 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!
was:
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!
> 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 check constuctor and method arguments 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)