[slf4j-dev] [Bug 311] New: Enable swapping of NOPLogger in SubstituteLoggerFactory

[bugzilla-daemon at qos.ch]

http://bugzilla.slf4j.org/show_bug.cgi?id=311

          Priority: P5
            Bug ID: 311
          Assignee: slf4j-dev at qos.ch
           Summary: Enable swapping of NOPLogger in
                    SubstituteLoggerFactory
          Severity: enhancement
    Classification: Unclassified
                OS: Linux
          Reporter: chetan.mehrotra at gmail.com
          Hardware: PC
            Status: NEW
           Version: 1.7.x
         Component: Core API
           Product: SLF4J

Currently the SubstituteLoggerFactory returns a NOPLogger while the
LoggerFactory is getting initialzed. Due to this any Logger created during
initialization period are not useful for the lifetime of the system. This is
also explained here [1]. We are facing this issue while using Slf4j with
logback in Sling which is an OSGi applicatopn [2]

The fix suggested involves changes in the application using Slf4j. It would be
simpler if the SubstituteLoggerFactory returns some forms of
SubstitutableLogger which can delegate to a different logger impl. By default
it uses NOPlogger. But later the delegate can be set to actual logger.

[1] http://www.slf4j.org/codes.html#substituteLogger
[2] https://issues.apache.org/jira/browse/SLING-3340

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/slf4j-dev/attachments/20140203/0a479726/attachment.html>