Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-commons Wiki" for change notification.
The following page has been changed by SimonKitching: http://wiki.apache.org/jakarta-commons/Logging/FrequentlyAskedQuestions The comment on the change is: Minor tweaks ------------------------------------------------------------------------------ == When should I use commons-logging? == - Commons-logging is very important when writing libraries that might be used in other projects. If the + Commons-logging is very important when writing '''libraries''' that might be used in other projects. If the - library codes directly to a concrete logging library (eg log4j or java.util.logging) but the application + library directly calls a concrete logging library API (eg log4j or java.util.logging) but the application it is embedded in is using some other logging library then there is a problem. However if the library is using - commons-logging then commons-logging just auto-detects what real logging lib is used in the - surrounding application and adapts to it (or manual config can be used to override the auto-detection) - so that the libraries' output and the application's output is all nicely unified. + commons-logging then commons-logging simply forwards all calls to whatever logging library the surrounding + application is using, ensuring output is all nicely unified. The specific underlying library commons-logging uses can be + explicitly configured (recommended), or commons-logging can be permitted to auto-detect it. - Commons-logging can be useful when you are writing an application but want to allow the person installing + Commons-logging can also be useful when you are writing an '''application''' but want to allow the person installing your app to choose what logging lib to use. Apache Tomcat does this; the person installing it can choose to use log4j, java.util.logging, etc. There is some debate over how useful this actually is. - Commons-logging can also be useful when you are writing an application but want to reserve the right to + Commons-logging can also be useful when you are writing an '''application''' but want to reserve the right to swap logging libraries at a later date. This is not so important, though, as it really isn't that hard to use some refactoring tool or a few scripts to change source code from using library X to library Y. @@ -63, +63 @@ == How Do I Change The Logging System Configuration? == The configuration supported by JCL is limited to choosing the underlying logging system. JCL does not (and will never) support changing the configuration of the wrapped logging system. Please use the mechanisms provided by the underlying logging system. + + The only exception is when using the !SimpleLog logging facility built into commons-logging. In this case, see the documentation for that class + for details on configuring logging levels. == Should I declare Log references static or not? == --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
