+1. This is an email I keep meaning to send to Commons - should Commons components that are 1.4+ depend on commons-logging.
Hen On 7/27/06, D&J Gredler <[EMAIL PROTECTED]> wrote:
I like that slf4j fixes jcl classloading issues, and that the parametrization of the logging methods allows you to remove that extra call to isXxxEnabled(). But what about JDK logging, since Tap5 is targetted at Java 5+? I keep waiting for the need for logging facades to go away, and it nevery happens :-) On 7/27/06, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > > A pretty common complaint is that commons-logging is a problem. It > does some wierd and awkward class loading things that ultimately > result in memory leaks. > > An alternative is SL4J: > > http://www.slf4j.org/ > > It has an improved API over commons-logging, making it easier to build > out complex messages. > > It's basic claim to fame is that it is statically bound. There are > different implementations of the framework for different toolkits. We > could bind to the log4j version for testing and building, and users > will bind to a specific version for deployment. > > It is under the X11 license (compatible with the ASL). > > The only problem is that the code is not quite threadsafe, something I > can address inside Tapestry 5 code. > > Thoughts? > > -- > Howard M. Lewis Ship > TWD Consulting, Inc. > Independent J2EE / Open-Source Java Consultant > Creator and PMC Chair, Apache Tapestry > Creator, Apache HiveMind > > Professional Tapestry training, mentoring, support > and project work. http://howardlewisship.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
