[
https://issues.apache.org/jira/browse/NIFI-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183125#comment-15183125
]
ASF GitHub Bot commented on NIFI-1595:
--------------------------------------
GitHub user olegz opened a pull request:
https://github.com/apache/nifi/pull/260
NIFI-1595 fixed ReflectionUtils to honor bridge methods
Refactored and simplified ReflectionUtils while at it
Added ReflectionUtilsTest
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/olegz/nifi NIFI-1595
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/260.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #260
----
commit e887ac52ae948fe4546903aa4442d64f2d6b3113
Author: Oleg Zhurakousky <[email protected]>
Date: 2016-03-06T19:46:35Z
NIFI-1595 fixed ReflectionUtils to honor bridge methods
Refactored and simplified ReflectionUtils while at it
Added ReflectionUtilsTest
----
> ReflectionUtils doesn't take into account "bridge" methods when checking if
> method is annotated
> -----------------------------------------------------------------------------------------------
>
> Key: NIFI-1595
> URL: https://issues.apache.org/jira/browse/NIFI-1595
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Oleg Zhurakousky
> Assignee: Oleg Zhurakousky
> Fix For: 0.6.0
>
>
> When extending from parameterized class some times compiler feels there is a
> need to generate a synthetic “bridge” method modeled after the one in super
> class. The issue is that annotations (if any) are not propagated to the
> synthetic method and not visible when reflecting on such method, essentially
> creating a condition where a standard lifecycle method (e.g., OnStopped) is
> not executed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
