[
https://issues.apache.org/jira/browse/LOG4J2-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Brouwer updated LOG4J2-562:
---------------------------------
Attachment: log4j2-loggerExtension.patch
This log4j2-loggerExtension.patch is in no way complete, but I would like some
feedback on the direction I am taking on this.
> Improve ability to create custom extended logger
> ------------------------------------------------
>
> Key: LOG4J2-562
> URL: https://issues.apache.org/jira/browse/LOG4J2-562
> Project: Log4j 2
> Issue Type: Improvement
> Components: API
> Reporter: Bruce Brouwer
> Attachments: log4j2-loggerExtension.patch
>
>
> Create a LoggerExtension from the original logger which simply remembers the
> FQCN that will ultimately be the extension.
> Also by doing this, we can switch a bunch of methods that ended up being
> public back to protected. I'm guessing they became public so extensions could
> call them.
> This can simplify extensions (such as slf4j, jcl, custom extensions, logger
> streams) so they don't have to pass in the FQCN to that special log method on
> AbstractLogger anymore. Also, you don't have to wrap every extended log
> method with a check to see if the logging is enabled. Finally, you don't need
> to have any access to the MessageFactory. This even has to potential to
> eliminate AbstractLoggerWrapper.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
