Return-Path: Delivered-To: apmail-jakarta-commons-user-archive@www.apache.org Received: (qmail 18453 invoked from network); 8 Sep 2004 01:46:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 8 Sep 2004 01:46:35 -0000 Received: (qmail 10506 invoked by uid 500); 8 Sep 2004 01:46:25 -0000 Delivered-To: apmail-jakarta-commons-user-archive@jakarta.apache.org Received: (qmail 10474 invoked by uid 500); 8 Sep 2004 01:46:24 -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 10460 invoked by uid 99); 8 Sep 2004 01:46:24 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=DNS_FROM_RFC_ABUSE X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from [206.190.39.105] (HELO web52310.mail.yahoo.com) (206.190.39.105) by apache.org (qpsmtpd/0.28) with SMTP; Tue, 07 Sep 2004 18:46:23 -0700 Message-ID: <20040908014621.26148.qmail@web52310.mail.yahoo.com> Received: from [68.171.238.16] by web52310.mail.yahoo.com via HTTP; Tue, 07 Sep 2004 18:46:21 PDT Date: Tue, 7 Sep 2004 18:46:21 -0700 (PDT) From: Reid Pinchback Subject: Re: [Digester]how to debug in degister To: Jakarta Commons Users List In-Reply-To: <20040907094237.64645.qmail@web15710.mail.cnb.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Just to add my two cents to the other responses, Digester only uses two logging categories, "...Digester" and "...Digester.sax". That means that you can't use the usual Log4J config hacks of tweaking category priorities to reduce noise. You'll want to make effective use of all the Log4J options, in particular: - pattern layout options to show you the class and method being invoked (something folks tend not to use because of the performance hit - don't leave these on for long, just long enough to track down a problem). - filters to control which messages you see. Here is an example of a log4.xml file that will let you do both. The filters are commented out so that initially you get all Digester DEBUG and Digester.sax INFO messages. If you uncomment the filters then you'll restrict yourself to messages that contain the specified string (ObjectCreateRule in this case). You can add more StringToMatch filters to allow more and more log messages through; the final DenyAllFilter junks anything you don't want. --- Gao Di wrote: > i find the setlogger() and getlogger() method in > digester,but i have never used any log api,anyone > can > tell me how to use it and let me see the log > infomation to help me debug? > > _________________________________________________________ > Do You Yahoo!? > 150����MP3����ѣ������������ֵ��� > http://music.yisou.com/ > ��Ů����Ӧ�о��У��ѱ���ͼ����ͼ�Ϳ�ͼ > http://image.yisou.com > 1G����1000�ף��Ż������������ݣ� > http://cn.rd.yahoo.com/mail_cn/tag/1g/*http://cn.mail.yahoo.com/event/mail_1g/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > commons-user-unsubscribe@jakarta.apache.org > For additional commands, e-mail: > commons-user-help@jakarta.apache.org > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-user-help@jakarta.apache.org