Why not a service locator pattern for hooking into the logging implementations?
Make a commons-logging-api.jar which has all the core pieces. Then, say a commons-logging-log4j.jar which has strictly the log4j classes, a description file, which the LogFactory searches for at runtime to find implementation classes.
I'd be happy to code this up.
But this solution seems like it would still require a logging jar for beanutils, even if a beanutils
user didn't care about logging. The point of this discussion seems to be how to make
commons-logging a truly optional dependency.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
