Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 32587 invoked from network); 1 Nov 2002 05:34:00 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 1 Nov 2002 05:34:00 -0000 Received: (qmail 166 invoked by uid 97); 1 Nov 2002 05:34:59 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 147 invoked by uid 97); 1 Nov 2002 05:34:59 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 133 invoked by uid 50); 1 Nov 2002 05:34:58 -0000 Date: 1 Nov 2002 05:34:58 -0000 Message-ID: <20021101053458.131.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: commons-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 14155] New: - Access to underlying native logging provider missing X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . 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: For additional commands, e-mail: