Revision as of 21:10, 24 May 2011 edit Daniel.Cardenas (talk \| contribs) Extended confirmed users, Pending changes reviewers 11,527 edits →Feature comparison: Deleted uncited text: Not widely used{{Citation needed\|date=August 2009}} ← Previous edit		Revision as of 21:12, 24 May 2011 edit undo Daniel.Cardenas (talk \| contribs) Extended confirmed users, Pending changes reviewers 11,527 edits →Summary: deleted uncited text: log4j is the leader in the Java Logging ___domain{{Citation needed\|date=June 2008}}. log4j has been around for a long time and has lots of support from the development community. It's simple to implement in an ap Next edit →
Line 103: ==Summary== [[log4j]] is the leader in the Java Logging ___domain{{Citation needed\|date=June 2008}}. log4j has been around for a long time and has lots of support from the development community. It's simple to implement in an application, yet has powerful tools built in to accomplish logging tasks. It is also easily extensible to handle proprietary needs. Apache Commons Logging isn't really a logging framework, but a wrapper for one. As such, it requires a logging framework underneath it. It is particularly useful when developing reusable libraries which need to write to whichever underlying logging system is being used by the application. It also provides flexibility in heterogeneous environments where the logging framework is likely to change, although in most cases, once a logging framework has been chosen, there is little need to change it over the life of the project.

Java logging framework: Difference between revisions