Hi Ceki,
In our case we are modeling the behavior of a legacy logging system, so
we have extended LoggerContext and override customizeNewLogger() to
inject the logger with existing appenders and attributes that fine tune
the logging according to the legacy product's settings.
Best regards,
Richard
------ Original Message ------
From "logback developers list via logback-dev" <logback-dev@qos.ch>
To logback-dev@qos.ch
Cc "logback developers list" <logback-dev@qos.ch>
Date 4/11/2024 2:10:00 PM
Subject [logback-dev] [JIRA] (LOGBACK-1747) Allow subclasses of
LoggerContext to customize new Logger instances
Ceki Gülcü
<https://jira.qos.ch/secure/ViewProfile.jspa?name=ceki>commented on
Improvement
LOGBACK-1747 <https://jira.qos.ch/browse/LOGBACK-1747>
Re: Allow subclasses of LoggerContext to customize new Logger instances
<https://jira.qos.ch/browse/LOGBACK-1747>
Richard Sand <https://jira.qos.ch/secure/ViewProfile.jspa?name=rsand>
Can you describe the customization?
Add Comment
<https://jira.qos.ch/browse/LOGBACK-1747#add-comment> Add Comment
<https://jira.qos.ch/browse/LOGBACK-1747#add-comment>
This message was sent by Atlassian Jira (v9.6.0#960000-sha1:a3ee8af)
Atlassian logo
_______________________________________________
logback-dev mailing list
logback-dev@qos.ch
https://mailman.qos.ch/cgi-bin/mailman/listinfo/logback-dev
