You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <di...@incubator.apache.org> on 2005/07/27 08:08:17 UTC

[jira] Closed: (DIREVE-127) Enable log4j based monitor impls in server main

     [ http://issues.apache.org/jira/browse/DIREVE-127?page=all ]
     
Alex Karasulu closed DIREVE-127:
--------------------------------

    Resolution: Duplicate

Duplicates DIREVE-171

> Enable log4j based monitor impls in server main
> -----------------------------------------------
>
>          Key: DIREVE-127
>          URL: http://issues.apache.org/jira/browse/DIREVE-127
>      Project: Directory Server
>         Type: New Feature
>     Reporter: Alex Karasulu
>     Assignee: Alex Karasulu
>      Fix For: 0.9.1

>
> There is no logging rigged into the server at the moment.  We desparately need something and this should be a high priority item.  Basically all the monitors need to be implemented as commons logging monitors and fed to the JNDI provider somehow.
> Still trying to figure this one out.

-- 
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