[
https://issues.apache.org/jira/browse/ARIES-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182964#comment-15182964
]
Guillaume Nodet edited comment on ARIES-1500 at 3/7/16 1:01 PM:
----------------------------------------------------------------
This concrete example should work imho, because it's only based on runtime
types, but that's clearly different from your original use case.
Do you mind checking with the following changes ?
https://github.com/gnodet/aries/commit/d98e07b4548eb9c63db3086383aee4cf05830abc
was (Author: gnt):
This concrete example should work imho, because it's only based on runtime
types.
Do you mind checking with the following changes ?
https://github.com/gnodet/aries/commit/d98e07b4548eb9c63db3086383aee4cf05830abc
> 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)
