Hi Nick,
I might be completely off base in this particular case, but in general, a library-type component should NOT configure log4j and let the user do it. Of course, you can still document logging in your library, in particular by providing one or more sample configuration files. The point is that you should not *impose* a log4j config file on the end-user. In the case of application (and not a library), you can provide a default log4j configuration file, but you should be careful to allow the end-user change it if she wants to. As basic rule of thumb, you should view logging mostly as an end-user concern. I hope these general remarks are helpful to you rather than a distraction, At 12:55 PM 7/26/2005, Nick Faiz wrote:
Hi Ceki, Yes, that sounds like a good idea. Right now, imo, the main issue is to get the logging configuration in place - as a dependency in project.xml for apacheds, so people can use it. Afterwards, the pattern layout can change, the logging statements can be altered. The 'Better alternative based on format messages' in http://www.slf4j.org/faq.html#2.3 looks really good. Cheers, Nick
-- Ceki Gülcü The complete log4j manual: http://www.qos.ch/log4j/
