[
https://issues.apache.org/jira/browse/ARIES-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15179550#comment-15179550
]
Jean-Philippe CLEMENT edited comment on ARIES-1500 at 3/4/16 8:59 AM:
----------------------------------------------------------------------
Thank you for the converter doc, nice!
The problem is Blueprint Aries implementation is not type erasure but does not
handle generics correctly. On another hand, the Blueprint syntax cannot express
generic types... I guess we may say there is a bug... somewhere, but all this
can be easily solved by removing the half-working generics checking within
Aries :)
PS: Maybe this could be done via a config flag?
was (Author: jeanphi):
Thank you for the converter doc, nice!
The problem is Blueprint is not type erasure, cannot express generic types
within the syntax and does not handle generics correctly... I guess we may say
there is a bug... somewhere :)
> 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)
