DbUtils intentionally does not use logging but it is rather small and
doesn't really need it. Validator has very little logging usage and that
dependency could probably be removed. Most of what it used to log was
better handled by throwing an exception out to the framework to the users.
I like the fact that DbUtils is distributed as just a single dbutils.jar
but that's not a requirement I would place on other commons components.
David
--- Henri Yandell <[EMAIL PROTECTED]> wrote:
>
> (probably flamebait)
>
> Why do so many of our components require logging of some form or
> another?
> (usually commons-logging).
>
> I can see why a micro-framework like Digester might be nice to have
> debugging statements, and might want an error system better than
> Exceptions as the rules can be tricky to write sometimes, but for a
> simple
> component-library like beanutils it seems like overkill. Even if we were
> using java.util.logging, it would still seem like overkill for a library
> to require logging.
>
> The following all depend on logging. Seems like a lot:
>
> beanutils
> betwixt
> chain
> configuration
> digester
> el
> httpclient
> jexl
> jxpath
> latka
> launcher
> math
> modeler
> validator
>
> (sandbox)
> cli
> messenger
> periodicity
> resources
> scaffold
> sql
> threadpool
> vfs
> xo
>
>
> Hen
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
_______________________________
Do you Yahoo!?
Win 1 of 4,000 free domain names from Yahoo! Enter now.
http://promotions.yahoo.com/goldrush
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
