OK. The first phase of 2) is in. There is now a sax logger in Digester so that all the SAX events can be handled independent of Digester's actual work. I would actually suspect that the sax logger will rarely be used.
I have not given each rule its own logger yet. I think I can get around 3) for now if BeanUtils was a little more expressive with its messages. Does anyone object if I convert BeanUtils to use commons-logging? Scott > -----Original Message----- > From: Scott Sanders > Sent: Thursday, January 10, 2002 5:16 PM > To: Jakarta Commons Developers List > Subject: RE: [Digester] Logging updates > > > Nevermind on number 1. I will just use setLogger(). Sorry > for the confusion. > > > -----Original Message----- > > From: Scott Sanders > > Sent: Thursday, January 10, 2002 5:15 PM > > To: [EMAIL PROTECTED] > > Subject: [Digester] Logging updates > > > > > > Hey all, > > > > I was thinking about doing some more logging updates within > > Digester, and would just like to see if anyone has > > comments/suggestions/arguments/vetos about it. > > > > 1) Allow the base instance name to be set on the Digester > > class (the default is org.apache.commons.Digester). This is > > useful if your(my) framework uses more than one type of > > digester (server components/resources/etc). Basically just a > > setLoggerInstanceName(String instanceName) on Digester. > > > > 2) More loggers. I would like to break out all the SAX > > events into a separate Log object with the instance name of > > BASE + ".sax". Then I would like to have all the Rules in > > CVS use their own log (BASE + "." + classname). > > > > 3) The ability to set a logging threshold for a particular > > rule. I don't know about you guys, but I am loading megabyte > > sized documents and when I want the logging info, it is > > typically on a certain pattern. Rule would just have a > > setLogThreshold(int level), so only the ObjectCreateRule on > > the foo/bar/wumpus pattern logs its findings. > > > > What do you guys think? > > > > Scott > > > > -- > > To unsubscribe, e-mail: > > <mailto:commons-dev-> [EMAIL PROTECTED]> > > For > > additional commands, > > e-mail: <mailto:[EMAIL PROTECTED]> > > > > > > -- > To unsubscribe, e-mail: > <mailto:commons-dev-> [EMAIL PROTECTED]> > For > additional commands, > e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
