[ 
https://jira.qos.ch/browse/SLF4J-429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19113#comment-19113
 ] 

Pappy STĂNESCU commented on SLF4J-429:
--------------------------------------

It *is* possible to log at *any* level by calling 
{{java.util.logging.Logger.log}}, which is what actually jersey or any other 
application that wants to configure the level at runtime does.

See your test {{SLF4JBridgeHandlerTest.testLevels}} failing here 
[https://github.com/pa314159/slf4j/tree/SLF4J-429/failure]

> jul-to-slf4j still logs OFF level
> ---------------------------------
>
>                 Key: SLF4J-429
>                 URL: https://jira.qos.ch/browse/SLF4J-429
>             Project: SLF4J
>          Issue Type: Bug
>          Components: jul-to-slf4j
>    Affects Versions: 1.7.25
>            Reporter: Pappy STĂNESCU
>            Assignee: Ceki Gülcü
>              Labels: logging
>
> SLF4JBridgeHandler maps java.util.logging.Level.OFF to 
> LocationAwareLogger.ERROR_INT.
> This causes logging that has been turned off to still be logged at the ERROR 
> level.
> See this bug at work at https://github.com/jersey/jersey/issues/3527



--
This message was sent by Atlassian JIRA
(v7.3.1#73012)
_______________________________________________
slf4j-dev mailing list
slf4j-dev@qos.ch
http://mailman.qos.ch/mailman/listinfo/slf4j-dev

Reply via email to