aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARIES-1500) Conversion fails with generics
Date Fri, 04 Mar 2016 12:42:40 GMT

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

Guillaume Nodet commented on ARIES-1500:
----------------------------------------

I really disagree that it's half working ;-)
It's working perfectly with the limitation that it does not keep the type after an object
has been created (type erasure).
It's consistent, safe, and the limitations can be overcome with converters.

Anyway, if you're willing to add support for adding more type information to the runtime,
I don't have any problem with that, but this is clearly not on my todo list.  Patches welcomed
!

> Conversion fails with generics
> ------------------------------
>
>                 Key: ARIES-1500
>                 URL: https://issues.apache.org/jira/browse/ARIES-1500
>             Project: Aries
>          Issue Type: Bug
>          Components: Blueprint
>    Affects Versions: blueprint-core-1.5.0
>         Environment: All
>            Reporter: Jean-Philippe CLEMENT
>
> Let's take a bean with the method setSomething(Something<T>) called via blueprint
with another bean implementing Something => exception saying that bean conversion is not
possible. But, if I change the method signature without the generic type setSomething(Something),
then it works as expected.
> Blueprint should not care for the generic type as Java is type erasure and do not exceed
the spec.
> There is no nice work around. Have to change all APIs used via Blueprint and take note
for all deviations. This is really heavy.



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

Mime
View raw message