logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Goers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-151) Please facilitate subclassing Logger and LoggerContext (in org.apache.logging.log4j.core)
Date Wed, 06 Feb 2013 17:01:16 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13572569#comment-13572569
] 

Ralph Goers commented on LOG4J2-151:
------------------------------------

That is fine.  Even though you provided one patch I am reviewing the pieces one at a time.
                
> Please facilitate subclassing Logger and LoggerContext (in org.apache.logging.log4j.core)
> -----------------------------------------------------------------------------------------
>
>                 Key: LOG4J2-151
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-151
>             Project: Log4j 2
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 2.0-beta3
>            Reporter: Remko Popma
>         Attachments: FastLog4j-v2-for-beta4.zip, FastLog4j.zip, LOG4J2-151-patch-LoggerContext.txt,
LOG4J2-151-patch-Logger.txt
>
>
> I would like to create a custom logger, while reusing the org.apache.logging.log4j.core.Logger
functionality.
> The following two changes would make subclassing possible:
> * change visibility of method Logger$PrivateConfig#logEvent(LogEvent) (line 265) from
protected to public
> * change visibility of method LoggerContext#newInstance(LoggerContext, String) (line
310) from private to protected
> My use case is that I want to create an asynchronous Logger for low latency logging.
> This custom logger hands off control to a separate thread as early as possible. In my
case, AsynchAppender is not a good match for my requirements, as with that approach (a) the
logging call still needs to flow down the hierarchy to the appender, doing synchronization
and creating objects at various points on the way, and (b) when serializing the LogEvent,
the getSource() method is always called, which is expensive.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message