[ https://jira.qos.ch/browse/SLF4J-192?page=com.atlassian.jira.plugin.system.i... ] Joachim Durchholz commented on SLF4J-192: ----------------------------------------- @Ralph Your assumptions about me are mostly wrong, which is the usual risk when arguing ad hominem in the Internet. "Silly and arbitrary" - well, you're not giving any arguments beyond that value judgement, so I find it difficult to clear up any misunderstandings on your and my side. I find your post generally pretty vague - lots of belittling, very little arguments. You may have valid reasons to reject my points, but I don't see any arguments that I can respond to, so continuing at that level is pointless and I'll stop. But I will continue to call shenanigans at purely abstract arguments, unless it's clear that and in what way the abstractions apply.
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)