> -----Original Message----- > From: matthew.hawthorne [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 11, 2004 6:27 PM > To: Jakarta Commons Developers List > Subject: Re: [beanutils] remove dependency on commons-logging > > Alex Karasulu wrote: > > Sorry to step in late but has anyone considered the use of a generic > > event callback interface for use in monitoring. Beanutil classes can > > expose a BeanutilsMonitor interface with methods that are called by > > the executing code to monitor notable events such as failures and > > successful operations. > > > > [snip] > > > For example, I think that beanutils is justified in defining the types of > events that occur, but not necessarily in assigning logging levels > to these events.
Exactly the logging implementation of the monitor interface would handle the specifics of logging events at the various levels. > For example, sometimes when things aren't working with betwixt, I'll > enable > debug logging for org.apache.* (forgetting the huge mistake that I'm > making) > and then I'll be assaulted by millions of statements from betwixt, > digester, > beanutils, etc. Perhaps this is a bad example, but my point is it would > be nice to allow deeper customization of logging, without getting too > fancy. I think technique is as simple as it can get plus it gives you so much besides just being able to log. > However, I'm not sure that everyone will like this sort of thing -- some > may > think it's a bit too complicated. Hope not :-). It's out there if it takes and it might not but at least it has been considered with the rest of the options. Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
