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

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

Your statement that using OFF for Logger.log is a misuse of JUL is rather 
eccentric, JUL would throw by itself an ILA if the argument is not allowed.

Again, the use case is when the level is configured at runtime and when OFF is 
used to disable logging. The fact that SLF4J decides to log a record which is 
otherwise *not logged* in the absence of SLF4J is definitely wrong.

But it's your call in the end, and I already spent too much time on this issue.


> 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