Java logging framework: Difference between revisions

Revision as of 04:53, 6 August 2009

Revision as of 08:06, 8 August 2009

Line 1:

{{Article issues

{{Articleissues

| refimprove = June 2008

| OR = June 2008

Line 94:

| SEVERE WARNING INFO CONFIG FINE FINER FINEST

| Depends on the underlying framework; Default Sun JVM implementation has the following: ConsoleHandler, FileHandler, SocketHandler, MemoryHandler

| Not widely used{{factCitation needed|date=August 2009}}

| Comes with the JRE

|-

Line 113:

{{POV-section|date=December 2007}}

Of the major players, [[log4j]] is still the front runner in the Java Logging ___domain{{FactCitation needed|date=June 2008}}. The log4j project has been around for a long time and has lots of support from the development community. It's simple to implement, yet has powerful tools built in to accomplish most logging tasks. It is also easily extensible to handle proprietary needs.

The Jakarta Commons Logging isn't really a logging framework, but a logging framework wrapper. As such, it requires a logging framework underneath it. It would be useful in an heterogeneous environment where the logging framework is likely to change. However, in most cases, once a suitable logging framework has been chosen, there is little need to change it over the life of the project.

Line 135:

* [http://www.developer.com/java/other/article.php/1404951 Logging in Java Applications] article by Thornton Rose

{{DEFAULTSORT:Java Logging Framework}}

[[Category:Java platform]]