commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Jakarta Commons Wiki] Updated: Logging/ConfigurationAndDiscovery
Date Sat, 18 Dec 2004 19:22:27 GMT
   Date: 2004-12-18T11:22:27
   Editor: <>
   Wiki: Jakarta Commons Wiki
   Page: Logging/ConfigurationAndDiscovery

   no comment

Change Log:

@@ -26,6 +26,8 @@
 The discovery process has many problems. The current implementation works well in some containers,
less well in other containers and not at all in some environments. It has become clear that
no one discovery mechanism can work well in the range of environments in which commons-logging
may find itself deployed. This points towards a need for the discovery mechanism to be pluggable.

 The process of discovery should be encapsulated entirely within the discovery layer. Therefore,
there seems to be nothing to gain by adding a separate interface for discovery. So, the discovery
component should have a facade which extends Logger.
 The choice of the appropriate discovery implementation should be common throughout a particular
environment. For example, though a discovery implementation that knows how to isolate applications
is needed for a container environment, there is no need for the discovery process to vary
per application. Therefore, the neccessary configuration can be stripped down to the minimal:
a system property. This would give the name of the Logger implementation to be loaded and
@@ -43,6 +45,7 @@
 public Log getLog(Object parameter) throws LogConfigurationException

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message