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-547) Update LoggerStream API
Date Sat, 01 Mar 2014 19:21:19 GMT

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

Ralph Goers commented on LOG4J2-547:

I'm going to look at it a bit more after I apply the patch, but at first glance I like this
patch a lot more.

> Update LoggerStream API
> -----------------------
>                 Key: LOG4J2-547
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-547
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: API
>    Affects Versions: 2.0-rc1
>            Reporter: Matt Sicker
>             Fix For: 2.0
>         Attachments: 0001-PrintStream-API-update.patch, log4j2-loggerStream.patch
> I've got some ideas on how to improve the LoggerStream idea that I added a little while
ago. The main thing I'd like to do is extract an interface from it, rename the default implementation
to SimpleLoggerStream (part of the SimpleLogger stuff), and allow log4j implementations to
specify a different implementation if desired.
> In doing this, I'm not sure where specifically I'd prefer the getStream methods to be.
Right now, it's in Logger, but really, it could be in LoggerContext instead. I don't think
I should be required to get a Logger just to get a LoggerStream.
> Now if only the java.io package used interfaces instead of classes. This would be so
much easier to design!

This message was sent by Atlassian JIRA

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

View raw message