Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Date: Tue, 2 Sep 2014 02:54:20 +0000 (UTC)
From: "Matt Sicker (JIRA)" <jira@apache.org>
To: log4j-dev@logging.apache.org
Message-ID: <JIRA.12738338.1409626455000.7003.1409626460872@Atlassian.JIRA>
In-Reply-To: <JIRA.12738338.1409626455000@Atlassian.JIRA>
References: <JIRA.12738338.1409626455000@Atlassian.JIRA>
 <JIRA.12738338.1409626455764@arcas>
Subject: [jira] [Created] (LOG4J2-809) Move caller class reflection utils to
 API
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Matt Sicker created LOG4J2-809:
----------------------------------

             Summary: Move caller class reflection utils to API
                 Key: LOG4J2-809
                 URL: https://issues.apache.org/jira/browse/LOG4J2-809
             Project: Log4j 2
          Issue Type: Task
          Components: API
    Affects Versions: 2.1
            Reporter: Matt Sicker
            Assignee: Matt Sicker


In particular, ReflectiveCallerClassUtility should be moved into the API inside the util package. This will provide a nice alternative for making a new Throwable each time.

For an idea on why this can be useful, run the ReflectionBenchmark in log4j-perf and note the differences. It's rather significant.

Since this would go in the util package, it would be a non-public API. It would make sense for some very, very common utility classes like this to be in there.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org