Date: 2004-12-18T11:22:27 Editor: 82.38.65.173 <> Wiki: Jakarta Commons Wiki Page: Logging/ConfigurationAndDiscovery URL: http://wiki.apache.org/jakarta-commons/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. +http://www.apache.org/~rdonkin/layers.png + 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 used. @@ -43,6 +45,7 @@ public Log getLog(Object parameter) throws LogConfigurationException }}} +http://www.apache.org/~rdonkin/logging-classes.png ---- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
