[
https://issues.apache.org/jira/browse/ARIES-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15242805#comment-15242805
]
Christian Schneider commented on ARIES-1533:
--------------------------------------------
A null check probably will not hurt but I would like to first really understand
your use case. Can you give an example how this bean looks like?
> 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
>
> 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)
