[slf4j-dev] [Bug 191] New: Implement java.util.logging.LogManager for jul-to-slf4j
bugzilla-daemon at pixie.qos.ch
bugzilla-daemon at pixie.qos.ch
Tue Jul 13 19:21:17 CEST 2010
http://bugzilla.slf4j.org/show_bug.cgi?id=191
Summary: Implement java.util.logging.LogManager for jul-to-slf4j
Product: SLF4J
Version: 1.6.x
Platform: PC
OS/Version: Windows NT
Status: NEW
Severity: blocker
Priority: P1
Component: jul-to-slf4j
AssignedTo: slf4j-dev at qos.ch
ReportedBy: bryan at vancameron.net
SLF4J implements a single Logger for J.U.L. that redirects log statements to
SLF4J. This has significant performance implications as every log statement is
processedby J.U.L. so it can then be forwarded to SLF4J. To avoid this, SLF4J
should implement java.util.logging.LogManager and register this with J.U.L. to
handle log statements. This is how application servers are able to implement
their own logging system using the J.U.L. API without performance penalty.
So, for example, there would be an org.slf4j.jul.LogManager implementation of
java.util.logging.LogManager. This would then be registered with J.U.L. using
the system property "java.util.logging.manager".
--
Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the slf4j-dev
mailing list