commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 14155] New: - Access to underlying native logging provider missing
Date Fri, 01 Nov 2002 05:34:58 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14155>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14155

Access to underlying native logging provider missing

           Summary: Access to underlying native logging provider missing
           Product: Commons
           Version: 1.0 Final
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Logging
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: ch@ipin.com


Currently only class org.apache.commons.logging.impl.Jdk14Logger provides access
to the underlying logging provider through the method 'getLogger()'. It would be
extremely helpful if the interface org.apache.commons.logging.Log would specify
that in a way like 'Object getLogger();', so that all implementing classes would
have to allow access to the underlying logging provider.

The reason why this is very important to me (and I could imagine to a growing
number of users out there?) is that we dynamically configure the underlying
logging provider at runtime (e.g. usage of setLevel() in JDK 1.4 logger and
Log4j). Why that? Quite simple, we want to make the logging configuration
available through JMX.

--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message