logback / LOGBACK-1747 [Open] Allow subclasses of LoggerContext to customize new Logger instances
============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1747 ============================== Issue created ------------------------------ Richard Sand created this issue on 20/Jun/23 16:58 Summary: Allow subclasses of LoggerContext to customize new Logger instances Issue Type: Improvement Assignee: Logback dev list Components: logback-classic Created: 20/Jun/23 16:58 Priority: Major Reporter: Richard Sand Description: I've a use case where I am adapting Logback to work with a legacy product's proprietary log mechanism. I did this by creating a wrapper class around a {{Logger. }}But there is no hook to programmatically touch the {{Logger}} instances at creation-time. I submitted a pull request #635 ([https://github.com/qos-ch/logback/pull/635)] that addresses this by simply adding a method to {{LoggerContext }}that is invoked immediately after {{{}Logger.createChildByName(){}}}, which by default is a no-op but can be implemented by custom contexts. ============================== This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af) _______________________________________________ logback-dev mailing list logback-dev@qos.ch https://mailman.qos.ch/cgi-bin/mailman/listinfo/logback-dev
