Return-Path: Delivered-To: apmail-jakarta-commons-user-archive@www.apache.org Received: (qmail 31696 invoked from network); 27 Apr 2004 19:48:27 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 27 Apr 2004 19:48:27 -0000 Received: (qmail 42597 invoked by uid 500); 27 Apr 2004 19:48:11 -0000 Delivered-To: apmail-jakarta-commons-user-archive@jakarta.apache.org Received: (qmail 42469 invoked by uid 500); 27 Apr 2004 19:48:10 -0000 Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Users List" Reply-To: "Jakarta Commons Users List" Delivered-To: mailing list commons-user@jakarta.apache.org Received: (qmail 42453 invoked from network); 27 Apr 2004 19:48:09 -0000 Received: from unknown (HELO devolver.fgm.dev) (207.158.50.34) by daedalus.apache.org with SMTP; 27 Apr 2004 19:48:09 -0000 Received: from apache.org (localhost.localdomain [127.0.0.1]) by devolver.fgm.dev (8.12.8/8.12.8) with ESMTP id i3RJmEbH005922 for ; Tue, 27 Apr 2004 12:48:15 -0700 Message-ID: <408EB8FE.4060904@apache.org> Date: Tue, 27 Apr 2004 12:48:14 -0700 From: "matthew.hawthorne" User-Agent: Mozilla Thunderbird 0.5 (X11/20040208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jakarta Commons Users List Subject: Re: [logging] How can I set the log level on Jdk14Logger References: <20040427190815.UIQY1745.imf24aec.mail.bellsouth.net@franklin> In-Reply-To: <20040427190815.UIQY1745.imf24aec.mail.bellsouth.net@franklin> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Alex Karasulu wrote: > I would like to turn on "debug" level logging but I can't seem to figure > out how to do this in commons-logging without just accessing the > JDK1.4 logging mechanism which I don't want to do since this would > defeat the purpose for using commons-logging in the first place. That's exactly how you do it, and in my opinion, it doesn't defeat the purpose. commons-logging leaves the configuration of the underlying logging implementation to the user. Upon examining the different configuration methods of both log4j and java.util.logging, I think this was a good choice. You can also set the system property (I believe it's org.apache.commons.logging.log) so that you get a SimpleLog instance no matter what your environment looks like. The details are in the documentation. --------------------------------------------------------------------- To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-user-help@jakarta.apache.org