[ https://issues.apache.org/jira/browse/NIFI-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183641#comment-15183641 ]
ASF subversion and git services commented on NIFI-1595: ------------------------------------------------------- Commit 4ce7b679e17b14ae88991bf9132a144e068ac0f0 in nifi's branch refs/heads/master from [~ozhurakousky] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=4ce7b67 ] NIFI-1595 fixed ReflectionUtils to honor bridge methods Refactored and simplified ReflectionUtils while at it Added ReflectionUtilsTest This closes #260. Signed-off-by: Aldrin Piri <ald...@apache.org> With adjustments to formatting and whitespace. Signed-off-by: Aldrin Piri <ald...@apache.org> > 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)