RE: Custom Filter Question

2004-01-12 Thread Shapira, Yoav
t;Russ... > >-Original Message- >From: Shapira, Yoav [mailto:[EMAIL PROTECTED] >Sent: Monday, January 12, 2004 9:53 AM >To: Log4J Users List >Subject: RE: Custom Filter Question > > >Howdy, > >>cluttered. So I only want to see debug statements that inv

RE: Custom Filter Question

2004-01-12 Thread Pitre, Russell
uary 12, 2004 9:53 AM To: Log4J Users List Subject: RE: Custom Filter Question Howdy, >cluttered. So I only want to see debug statements that involve the >classes that I have written. I'll eventually turn the filter off in >production. Why not just add org.jboss=WARN to your co

RE: Custom Filter Question

2004-01-12 Thread Shapira, Yoav
Howdy, >cluttered. So I only want to see debug statements that involve the >classes that I have written. I'll eventually turn the filter off in >production. Why not just add org.jboss=WARN to your configuration file so that only messages at WARN level or higher show up from the org.jboss class

RE: Custom Filter Question

2004-01-12 Thread Pitre, Russell
uot; Man o' manI wish I would think things through before I ask the list for help :) Thanx Yaov- Russ -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Monday, January 12, 2004 9:34 AM To: Log4J Users List Subject: RE: Custom Filter Question Howdy,

RE: Custom Filter Question

2004-01-12 Thread Shapira, Yoav
Howdy, The parameter could be a comma-delimited string, which you could parse with a StringTokenizer very easily. But why are you doing this? Yoav Shapira Millennium ChemInformatics >-Original Message- >From: Pitre, Russell [mailto:[EMAIL PROTECTED] >Sent: Monday, January 12, 2004 9:33