[ https://jira.qos.ch/browse/SLF4J-192?page=com.atlassian.jira.plugin.system.i... ] Joachim Durchholz commented on SLF4J-192: ----------------------------------------- You have a backend dependency anyway. At least you have a logback.xml (or whatever configuration file you use). Whatever has this file - main program, application container, whatever - is also the right place to close logging resources. No facade is perfect - you need to set it up and tear it down somewhere. The point of a facade is not to remove all traces, it is to concentrate them in a single place where it is easy to control.
Need ability to shutdown loggers and flush appenders ----------------------------------------------------
Key: SLF4J-192 URL: https://jira.qos.ch/browse/SLF4J-192 Project: SLF4J Issue Type: Improvement Components: Core API Affects Versions: 1.6.x Environment: Operating System: All Platform: All Reporter: Michael Schall Assignee: SLF4J developers list
There needs to be a way to shutdown logging and flush async appenders so when a process is closing, all log events are written before the process is closed. Should ILoggerFactory have a shutdown or stop method? It could shutdown whatever logging back end I'm using? For log4j it would call - org.apache.log4j.LogManager.getLoggerRepository().shutdown(); For logback it would call - loggerContext.stop() Other back ends - ??? This is required to allow me to not reference logging back ends explicitly in my code to shutdown successfully without losing events. Discussion about this is happening on the user list at - http://www.qos.ch/pipermail/logback-user/2010-September/001816.html
-- This message was sent by Atlassian JIRA (v7.3.1#73012)