directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DIRAPI-127) org.apache.directory.ldap.client.api.SearchCursorImpl should use normal logger (not "CURSOR")
Date Fri, 05 Apr 2013 11:52:15 GMT

     [ https://issues.apache.org/jira/browse/DIRAPI-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Emmanuel Lecharny resolved DIRAPI-127.
--------------------------------------

    Resolution: Won't Fix

We not anymore use a "CURSOR" as a key to find the logger. The new version uses :

private static final Logger LOG_CURSOR = LoggerFactory.getLogger( Loggers.CURSOR_LOG.getName()
);

where Loggers.CURSOR_LOG value is "org.apache.directory.CURSOR_LOG"

You have a dedicated loggers for Cursors and tou can enable or disable the logs globaly using
the prefix (org.apach.directory).
                
> org.apache.directory.ldap.client.api.SearchCursorImpl should use normal logger (not "CURSOR")
> ---------------------------------------------------------------------------------------------
>
>                 Key: DIRAPI-127
>                 URL: https://issues.apache.org/jira/browse/DIRAPI-127
>             Project: Directory Client API
>          Issue Type: Bug
>    Affects Versions: 1.0.0-M15
>            Reporter: Hendy Irawan
>
> instead of the currently:
>     private static final Logger LOG_CURSOR = LoggerFactory.getLogger( "CURSOR" );
> it should use the standard
>     private static final Logger LOG_CURSOR = LoggerFactory.getLogger( SearchCursorImpl.class
);
> So it can be controlled consistently just like the other loggers in the application.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message