[
https://issues.apache.org/jira/browse/LOG4J2-868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14159729#comment-14159729
]
Matt Sicker commented on LOG4J2-868:
------------------------------------
Renamed the interface to ShutdownCallbackRegistry. Also making
Log4jContextFactory implement it in order to delegate. Thus, a
LoggerContextFactory can implement ShutdownCallbackRegistry to get the
additional functionality (though that might be a rather convoluted
customization of Log4j at that point what with mixing Log4j Core and random
parts substituted wholesale).
> Allow shutdown hook registration handling to be customizable
> ------------------------------------------------------------
>
> Key: LOG4J2-868
> URL: https://issues.apache.org/jira/browse/LOG4J2-868
> Project: Log4j 2
> Issue Type: New Feature
> Components: Core
> Affects Versions: 2.0.2
> Reporter: Matt Sicker
> Assignee: Matt Sicker
> Fix For: 2.1
>
>
> Besides the ability to enable or disable the shutdown hook, there should be a
> ShutdownRegistrationStrategy interface for customizing how to register a
> shutdown callback in LoggerContext. This will allow application servers to
> specify their own class that can register the shutdown callback for a
> LoggerContext.
> To make this really flexible, Log4jContextFactory should be the class that
> creates the ShutdownRegistrationStrategy.
> The basic idea behind this feature is already implemented. I'd like to make
> this API a bit better before 2.1 so we aren't stuck with a useless interface
> later on.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
