On Sun, 27 Mar 2005 20:21:04 +0200, Simon Kitching <[EMAIL PROTECTED]> wrote: > There really is no reason for an application to use JCL. I�m personally > surprised that Tomcat chose to do so for its internal logging, and > pleased to see that the next version is moving away from it.
That's news to me. > JCL is great for libraries, where the code *cannot* make any assumptions > about what logging library is available. However there is a significant > price to pay for using JCL: > * a "least common denominator API", and We have never needed anything more. > * a significant performance hit. JFluid didn't ever show logging as an issue, so it does not matter to me. > Application code which can make assumptions about what logging library > it will be bundled with should generally code directly to that logging > libraries�API. The app then gets a more complete API and better > performance. [1] > > And libraries which provide fairly simple functionality don�t need > logging at all; they can report problems via exceptions. > > But for libraries that are complex enough to need logging, but can�t > assume a particular logging implementation, what options are there other > than commons logging (or UGLI once it is released)? I would really be > interested to know! Hard-wiring the use of log4j into such a library > isn�t an option for obvious reasons. > > Please note that the above is just my personal view.. I don't think Tomcat has a buisiness deciding which logger people should use, just the same as for your libraries. -- xxxxxxxxxxxxxxxxxxxxxxxxx R�my Maucherat Developer & Consultant JBoss Group (Europe) S�RL xxxxxxxxxxxxxxxxxxxxxxxxx --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
