Apache Commons Logging Publisher's description
When writing a library it is very useful to log information.
When writing a library it is very useful to log information. However there are many logging implementations out there, and a library cannot impose the use of a particular one on the overall application that the library is a part of.
The Logging package is an ultra-thin bridge between different logging implementations. A library that uses the commons-logging API can be used with any logging implementation at runtime. Commons-logging comes with support for a number of popular logging implementations, and writing adapters for others is a reasonably simple task.
Applications (rather than libraries) may also choose to use commons-logging. While logging-implementation independence is not as important for applications as it is for libraries, using commons-logging does allow the application to change to a different logging implementation without recompiling code.
Note that commons-logging does not attempt to initialise or terminate the underlying logging implementation that is used at runtime; that is the responsibility of the application. However many popular logging implementations do automatically initialise themselves; in this case an application may be able to avoid containing any code that is specific to the logging implementation used.
What's New in This Release:Incompatibilities:
В· The protected method LogFactory.getContextClassLoader has been reverted to pre-1.1
В· behavior. In earlier releases, this method did not use an AccessController when
В· obtaining the context classloader. In version 1.1 it did. In this release, it has
В· reverted to not using an AccessController; any user-level code that needs to obtain
В· a context classloader should itself create an AccessController, and call the
В· LogFactory.getContextClassLoader method via the doPrivileged method. This fixes a
В· potential security issue, where untrusted code could get access to the context
В· classloader if a signed Commons Logging library was in the classpath.
В· LOGGING-106: Commons Logging 1.1 was completely unusable under a security policy that prevented access to system properties. Even signing/authorising the Commons Logging library was not sufficient. This has been fixed by (a) catching SecurityException and falling back to a sensible default, and (b) using AccessController so Com...
System Requirements:В· Java
Program Release Status: New Release
Program Install Support: Install and Uninstall