You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2010/05/15 08:59:46 UTC
[jira] Commented: (LOG4J2-5) Appenders, Layouts and other back-end
classes should be independent of logging API
[ https://issues.apache.org/jira/browse/LOG4J2-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12867820#action_12867820 ]
Ralph Goers commented on LOG4J2-5:
----------------------------------
In my experimental branch LogEvent is an interface. The Layout, Filter and Appender interfaces all use the LogEvent interface.
> Appenders, Layouts and other back-end classes should be independent of logging API
> ----------------------------------------------------------------------------------
>
> Key: LOG4J2-5
> URL: https://issues.apache.org/jira/browse/LOG4J2-5
> Project: Log4j 2
> Issue Type: Wish
> Components: Appenders
> Reporter: Curt Arnold
>
> Appenders and related classes should be able to work on a logging event interface and not be tied to a specific logging API and its native LoggingEvent class. The logging event interface should be readily implementable as a thin wrapper around established logging events such as o.a.l.spi.LoggingEvent and java.util.logging.LogRecord. log4j 2.0 appenders should be usable as java.util.logging.Handler's with a simple adapter.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org