logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Gregory (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LOG4J2-1066) Expose Log4jContextFactory's ShutdownCallbackRegistry
Date Mon, 22 Jun 2015 23:42:01 GMT

     [ https://issues.apache.org/jira/browse/LOG4J2-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Gary Gregory updated LOG4J2-1066:
    Summary: Expose Log4jContextFactory's ShutdownCallbackRegistry  (was: Expose ShutdownCallbackRegistry)

> Expose Log4jContextFactory's ShutdownCallbackRegistry
> -----------------------------------------------------
>                 Key: LOG4J2-1066
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1066
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Plugins
>    Affects Versions: 2.2, 2.3
>            Reporter: Charles Allen
> Currently the instance created by org.apache.logging.log4j.core.impl.Log4jContextFactory#createShutdownCallbackRegistry
in the default constructor for Log4jContextFactory is not acquirable without resorting to
reflection. As such, any class which implements ShutdownCallbackRegistry is not able to get
the actual instance of itself and must resort to either reflection or static methods to properly
shutdown in an arbitrary lifecycle workflow.
> This ask is to better clarify how a custom implementation of ShutdownCallbackRegistry
can get its instance.

This message was sent by Atlassian 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