On Wed, 27 Mar 2002, Ceki G�lc� wrote: > If your library chooses to use logging API XYZ, this does not impose > XYZ to the clients of your library. Your clients can use the logging > library they prefer (if they are using logging API) and your library > can use XYZ.
And the user will have to configure and use 2 loggers. Or maybe 3, 4 or more - depending on how many libraries he uses. If I write an application and I choose log4j, I would like a single config file and a consistent behavior for all the components. Same if I choose logkit or jdk1.4. The user ( or tomcat, etc ) may have scripts, UI, security settings etc. > One choice does not necessarily influence the other. For > example, the fact that JBoss uses log4j does not impose a logging > library to the bean developer. Similarly, Tomcat's logging library > does not prevent web-app developers from using log4j. If the bean developer is using commons-logging, he'll benefit of whatever user interface/setting/controls Jboss or tomcat provides. Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
