Return-Path: X-Original-To: apmail-nifi-commits-archive@minotaur.apache.org Delivered-To: apmail-nifi-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 27AD41891F for ; Mon, 7 Mar 2016 20:10:41 +0000 (UTC) Received: (qmail 78166 invoked by uid 500); 7 Mar 2016 20:10:41 -0000 Delivered-To: apmail-nifi-commits-archive@nifi.apache.org Received: (qmail 78131 invoked by uid 500); 7 Mar 2016 20:10:41 -0000 Mailing-List: contact commits-help@nifi.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@nifi.apache.org Delivered-To: mailing list commits@nifi.apache.org Received: (qmail 78022 invoked by uid 99); 7 Mar 2016 20:10:41 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Mar 2016 20:10:41 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id D082B2C1F6B for ; Mon, 7 Mar 2016 20:10:40 +0000 (UTC) Date: Mon, 7 Mar 2016 20:10:40 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: commits@nifi.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (NIFI-1595) ReflectionUtils doesn't take into account "bridge" methods when checking if method is annotated MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/NIFI-1595?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D15183= 614#comment-15183614 ]=20 ASF GitHub Bot commented on NIFI-1595: -------------------------------------- Github user olegz commented on the pull request: https://github.com/apache/nifi/pull/260#issuecomment-193428093 =20 np, most of the formatting was done to javadocs since they were too lon= g. Is that the changes you are referring to? Just curious > 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 i= s a need to generate a synthetic =E2=80=9Cbridge=E2=80=9D method modeled af= ter 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)