[ http://jira.qos.ch/browse/LBCLASSIC-102?page=com.atlassian.jira.plugin.syste... ] Joern Huxhorn commented on LBCLASSIC-102: ----------------------------------------- Ralph is right. I recently also realized that Logger instances are kept in a Hashtable and I was wondering if a WeakHashMap wouldn't be a much better choice. Even if the performance is slightly worse with WeakHashMap (that has similar performance as HashMap), preventing the garbage-collection of unused loggers is, more or less, a bug.
Suggestion: Change logger name of inner classes. ------------------------------------------------
Key: LBCLASSIC-102 URL: http://jira.qos.ch/browse/LBCLASSIC-102 Project: logback-classic Issue Type: Improvement Components: appender Affects Versions: 0.9.15 Reporter: Joern Huxhorn Assignee: Ceki Gulcu Fix For: 0.9.18
At the moment, the logger name of inner classes is OuterClass$InnerClass. Because of that, the logging level of OuterClass isn't inherited by InnerClass at the moment. If LoggerFactory changed the logger name to OuterClass.InnerClass instead, InnerClass would inherit the logging level of OuterClass which seems intuitively correct. I'd suggest to accept both $InnerClass and .InnerClass style in logback configurations for compatibility and usability reasons.
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira