You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Charles Allen (JIRA)" <ji...@apache.org> on 2015/06/23 00:28:02 UTC
[jira] [Created] (LOG4J2-1066) Expose ShutdownCallbackRegistry
Charles Allen created LOG4J2-1066:
-------------------------------------
Summary: Expose ShutdownCallbackRegistry
Key: LOG4J2-1066
URL: https://issues.apache.org/jira/browse/LOG4J2-1066
Project: Log4j 2
Issue Type: Improvement
Components: Plugins
Affects Versions: 2.3, 2.2
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
(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