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 On 7/26/05, Ceki Gulcu (JIRA) <[EMAIL PROTECTED]> wrote: > [ > http://issues.apache.org/jira/browse/DIREVE-171?page=comments#action_12316730 > ] > > Ceki Gulcu commented on DIREVE-171: > ----------------------------------- > > Nick, > > I appreciate your work on setting up nlog4j at ibiblio. Thank you. > > You might want to consider using format patterns as described in [1, 2]. > Just to let you know an alternative exists, > > [1] http://www.slf4j.org/manual.html (see section "Typical usage pattern") > [2] http://www.slf4j.org/faq.html#2.3 > > Cheers, > > > add log4j config patch > > ---------------------- > > > > Key: DIREVE-171 > > URL: http://issues.apache.org/jira/browse/DIREVE-171 > > Project: Directory Server > > Type: Improvement > > Components: server main > > Versions: 0.9.1 > > Reporter: Nick Faiz > > Assignee: Alex Karasulu > > Priority: Trivial > > Attachments: log4j.properties, log_patch2.txt, logging_patch.txt, > > logging_patch_3.txt > > > > Please find enclosed a patch (diff file) and a log4j.properties file. > > You should create a src/etc directory for main and core and place the > > properties file there. > > Cheers, > > Nick > > -- > This message is automatically generated by JIRA. > - > If you think it was sent incorrectly contact one of the administrators: > http://issues.apache.org/jira/secure/Administrators.jspa > - > For more information on JIRA, see: > http://www.atlassian.com/software/jira > >
