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]
This sounds interesting, and for lower-level libraries I think it actually makes more sense -- giving more power to the user.
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.
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.
However, I'm not sure that everyone will like this sort of thing -- some may think it's a bit too complicated.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
