[
https://issues.apache.org/jira/browse/ARIES-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15880376#comment-15880376
]
Christian Schneider commented on ARIES-1674:
--------------------------------------------
Ok .. got it now.
I am not a specialist in generics but I assume that in the compiled code the
actual class ReportDAO is lost. At the level of AbstractPersistenceManager we
only know that DAO extends AbstractJpaDao and that is why Aries JPA injects the
object as this type. I have no idea how to fix that.
> Multiple inharitance levels with generics cause ClassCastException when JPA
> is enabled
> --------------------------------------------------------------------------------------
>
> Key: ARIES-1674
> URL: https://issues.apache.org/jira/browse/ARIES-1674
> Project: Aries
> Issue Type: Bug
> Components: JPA
> Affects Versions: jpa-2.5.0
> Environment: Win 7 x64, JDK 1.8.0_73, Karaf 4.0.4
> Reporter: Felix Wassmer
> Assignee: Christian Schneider
>
> I'm using inheritance with generics over multiple levels.
> Injecting properties to those beans works fine, but on access of a property
> of the lowest class, there is a ClassCastException thrown.
> I could narrow it down to enabling JPA in the blueprint causing the issue:
> When disabling JPA, the proper bean class is resolved,
> enabled the type resolving stopped at the parent abstract class of the
> expected class, thus throwing a ClassCastException.
> Example project to reproduce this issue:
> https://github.com/fwassmer/inheritance
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
