--- Ceki Gülcü <[EMAIL PROTECTED]> wrote: > At 11:21 29.01.2003 +0100, Dani Estermann wrote: > >Has jakarta got a strategy/guideline/regulation > that recommends a certain > >logging api to be used by jakarta projects? Are > existing and future > >jakarta projects allowed to choose between log4j, > LogKit, commons-logging > >or even JDK1.4-Logging? > > > >We are currently choosing a logging api and > implementation to be used > >in our business projects. While I favor the power > of the log4j > >implementation, I ask myself if it would be wise to > use a -- maybe more > >future-proof -- thin bridge like commons-logging on > top. > > I believe log4j is here to stay. Its user base is > large and > growing. As time passes, more people will gravitate > to it as it keeps > improving. We have enough cool features in pipe to > keep us busy for > the foreseeable future. Simile, the future is bright > and open!
I agree with Ceki, Log4j has a bright future indeed. If it were my project, I'd pick Log4J first, then the Merlin logging (even if I were using JDK 1.4). I don't known too much about LogKit, but it's probably fine as well. Don't use commons-logging unless you're absolutely sure you need it. If you are distributing your code to other companies, then you might have an argument for a logging facade in order to plug into their logging framework. However, if your code is intended for internal use only, using a facade is more work with no benefit. - Morgan > >Daniel > > -- > Ceki > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > ===== Morgan Delagrange http://jakarta.apache.org/taglibs http://jakarta.apache.org/commons http://axion.tigris.org http://jakarta.apache.org/watchdog __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
