Talk:Java logging framework

NPOV
The summary paragraphs on log4j and Java Logging make it appear that log4j should be used just because it is more popular, but log4j is more popular because it has been in existence longer. Rewriting these two paragraphs would improve the neutrality. LanceHelsten (talk) 18:21, 28 November 2007 (UTC)


 * I could do a when/where, but it would be opinion.


 * Log4J: works on older Java versions (not so relevant), really good loggers, good configuration by in-classpath files and API.
 * Commons-Logging. Not a real logger, just a wrapper around 3 logging APIs, one of which (avalon logkit) is obsolete and never encountered in the wild. By adopting commons-logging in a library, you give whoever uses the app their own choice of what to use behind it.
 * Java Logging API. built in to the JVM. Hard to configure -external files only. Not easily changed on the fly. No useful output formats.
 * SL4J. Switch logging by using different libraries.
 * printing to standard output channels directly. Useful when logging hasn't even been bootstrapped yet. SteveLoughran (talk) 13:06, 6 March 2008 (UTC)


 * From the comparison between the talk page and current section text, I believe an editor forgot to remove the NPOV tag, so I did. --   Alain R 3 4 5   Techno-Wiki-Geek    00:26, 7 January 2010 (UTC)

measuring popularity
I see a citation is demanded for assessing popularity. The Apache Maven repositories can be used to determine dependencies on commons-logging, log4j and others, such as this listing of log4j's use: []. However, detecting use of the java logging API would need introspection on the libraries in the repository itself. It could be possible to do this and write a paper on the subject, one wikipedia could cite. Note that as commons-logging is not a logger so much as an Extra Layer of Indirection; if commons-logging+log4j are found together, it means log4j is used via commons-logging APIs. SteveLoughran (talk)

categories, popularity and commons logging
AFAIK this article should describe Logging Frameworks (log4j, Java SDK Logger, Logback) and Logging Wrappers (Commons Logging and SLF4J) and clearly separate them.

Logging Frameworks simplyfi application development by eliminating the popular System.out usage with a meaningfull API and a configurable and extendable backend to output the Log entries to the console, files or even databases.

Logging Wrapper help application and library developers to provide logging independant from the chosen logging framework.

It would also help to at least mention the discussion around commons logging and classloaders, like this reference: Spring Framework reference 3.0 Chapter 1.3.2.1 Not using commons logging "Unfortunately, the runtime discovery algorithm in commons-logging, while convenient for the end-user, is problematic. If we could turn back the clock and start Spring now as a new project it would use a different logging dependency." []

--178.24.246.195 (talk) 22:44, 13 December 2011 (UTC)