You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Christian Schneider (JIRA)" <ji...@apache.org> on 2016/04/18 10:03:25 UTC
[jira] [Resolved] (ARIES-1533) JPA blueprint AnnotationScanner is
unable to handle Interfaces
[ https://issues.apache.org/jira/browse/ARIES-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Schneider resolved ARIES-1533.
----------------------------------------
Resolution: Fixed
I have committed a test and fix. Please validate that it actually solves your problem.
> JPA blueprint AnnotationScanner is unable to handle Interfaces
> --------------------------------------------------------------
>
> Key: ARIES-1533
> URL: https://issues.apache.org/jira/browse/ARIES-1533
> Project: Aries
> Issue Type: Bug
> Components: JPA
> Affects Versions: jpa-2.3.0
> Reporter: Jurriaan Heuberger
> Assignee: Christian Schneider
> Fix For: jpa-2.4.0
>
>
> If there are beans defined in the blueprint with a "class" attribute referencing an interface instead of a class, the JPA blueprint AnnotationScanner fails with a NullPointerException.
> During the annotation scanning, the assumption is made that the class hierarchy will eventually hit the Object.class, while an interface Class<?> will return null when the getSuperclass() is called.
> While it may not be a common use case to reference an Interface in a bean definition, I have a rather specific use case where I am using a factory class with a factory method to return an implementation of an interface.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)