logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Tucker (JIRA)" <j...@apache.org>
Subject [jira] [Created] (LOG4J2-248) Log4jContextListener: Use Thread instead of Class for fallback classloader
Date Thu, 09 May 2013 22:59:18 GMT
Tim Tucker created LOG4J2-248:

             Summary: Log4jContextListener: Use Thread instead of Class for fallback classloader
                 Key: LOG4J2-248
                 URL: https://issues.apache.org/jira/browse/LOG4J2-248
             Project: Log4j 2
          Issue Type: Improvement
    Affects Versions: 2.0-beta5
            Reporter: Tim Tucker
            Priority: Minor

I was experimenting with creating my own context listener based on Log4jContextListener and
noticed that the call in getClassLoader to get the class's classloader was triggering a PMD

The rule's notes indicate that Thread.currentThread().getContextClassLoader() might return
more reliable results than Object.class.getClassLoader().

The code in question is as follows:
try {
    // if container is Servlet 3.0, use its getClassLoader method
    return (ClassLoader)context.getClass().getMethod("getClassLoader").invoke(context);
} catch (Exception ignore) {
    // otherwise, use this class's class loader
    return Log4jContextListener.class.getClassLoader();

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

View raw message