[
https://issues.apache.org/jira/browse/ARIES-1341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14612017#comment-14612017
]
Christian Schneider commented on ARIES-1341:
--------------------------------------------
No problem. I am happy to get such detailed feedback.
I am not sure what to do about the karaf jpa feature. If you configure your own
dependencies correctly it will work but with a slight error it will load both
persistence api versions and cause the problems you had. I will work around it
by providing good documentation so people are at least aware of it. I am not
sure how to solve the problem though. Maybe aries jpa could detect that more
than one version is present and log a warning.
As we basically talk about 3 independent improvements I propose we use separate
issues for them.
> JpaBeanProcessor not working in karaf
> -------------------------------------
>
> Key: ARIES-1341
> URL: https://issues.apache.org/jira/browse/ARIES-1341
> Project: Aries
> Issue Type: Improvement
> Components: Blueprint, JPA
> Affects Versions: jpa-2.0.0
> Environment: karaf-4.0.0, java 8
> Reporter: Michał Woś
> Assignee: Christian Schneider
> Fix For: jpa-2.1.0, jpa-2.0.1
>
>
> * getAnnotation() return null because annotations are proxied (com.sun.proxy).
> * only top level class is scanned. super classes are not
> * only fields are scanned whereas target of persistence annotations is: TYPE,
> METHOD, FIELD
> * Setting persistence fields results in:
> Can not set javax.persistence.EntityManager field xxx to
> com.sun.proxy.$Proxy37
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
