aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARIES-1533) JPA blueprint AnnotationScanner is unable to handle Interfaces
Date Mon, 18 Apr 2016 08:02:25 GMT

    [ https://issues.apache.org/jira/browse/ARIES-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15245266#comment-15245266
] 

ASF subversion and git services commented on ARIES-1533:
--------------------------------------------------------

Commit 1739703 from [~chris@die-schneider.net] in branch 'aries/trunk'
[ https://svn.apache.org/r1739703 ]

[ARIES-1533] Make sure interfaces do not cause a NPE

> 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)

Mime
View raw message