logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Sicker (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-711) Add native support for using Log4j in Jetty
Date Mon, 14 Jul 2014 01:18:04 GMT

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

Matt Sicker commented on LOG4J2-711:

Or would this be more appropriate to request at Jetty?

> Add native support for using Log4j in Jetty
> -------------------------------------------
>                 Key: LOG4J2-711
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-711
>             Project: Log4j 2
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 2.0
>         Environment: At least Jetty 9.2, but it wouldn't be hard to support Jetty 8.x,
possibly even Jetty 7.x
>            Reporter: Matt Sicker
>            Priority: Minor
> Jetty provides a pretty simple [Logger API|http://download.eclipse.org/jetty/stable-7/apidocs/org/eclipse/jetty/util/log/Logger.html]
which can be implemented by custom logging frameworks. You can set the {{"org.eclipse.jetty.util.log.class"}}
system property to the FQCN of your logger implementation.
> Jetty does provide an SLF4J-based implementation, but our SLF4J bridge doesn't support
setting the logger level dynamically. The log4j-core Logger class, however, does.
> There is one caveat, however. Such an implementation should probably document that you
should NOT use the ServletAppender. This can be checked reflectively for the presence of the
Jetty logger for at least outputting a warning message about it.

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