[ http://issues.apache.org/jira/browse/DIRSNICKERS-113?page=all ]
Alex Karasulu resolved DIRSNICKERS-113:
---------------------------------------
Resolution: Fixed
Fixed it in 332800.
> BERDigester does not follow this convention for logging category names
> ----------------------------------------------------------------------
>
> Key: DIRSNICKERS-113
> URL: http://issues.apache.org/jira/browse/DIRSNICKERS-113
> Project: Directory ASN1
> Type: Improvement
> Reporter: Stefan Zoerner
> Assignee: Alex Karasulu
> Priority: Minor
>
> As described on the dev mailing list by Simon Temple:
> ... it took a long time to stop the BERDigester DEBUG messages filling up our
> log files. By convention most projects that use logging create loggers using
> their class names:LoggerFactory.getLogger( InterceptorChainTest.class ); So
> controlling logging system wide is quite intuitive.
> The BERDIgester does not follow this convention. It creates a logger with a
> fixed name "BERDigester".
> org.apache.asn1.ber.digester.BERDigesterLoggingMonitor
> Can/should this be changed?
--
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
