[
http://jira.qos.ch/browse/LBCLASSIC-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11459#action_11459
]
Ceki Gulcu commented on LBCLASSIC-102:
--------------------------------------
Syvalta - 15/Dec/09 10:15 AM About markers, they seems to have one major
downside: you need to include the marker in every single log statement. Perhaps
some kind of lightweight and garbage collectible wrapper delegating to the
actual log instance could be a generic solution to this "include instance id"
problem?
Indeed, the markers have to added to each log statement where they are wanted
However, you could automatically add the appropriate marker via some code in
the objects you wish to track. It should be relatively easy to do.
> 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
_______________________________________________
logback-dev mailing list
logback-dev@qos.ch
http://qos.ch/mailman/listinfo/logback-dev
