[
https://issues.apache.org/jira/browse/LOG4PHP-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13165970#comment-13165970
]
Ivan Habunek commented on LOG4PHP-162:
--------------------------------------
In fact, looking at it, I think that we should fix LoggerLevel::toLevel() so
that it does not return DEBUG level when defaultLevel is set to null. I believe
that it should return null in that case.
The configurator can issue a warning and handle the situation (either use
default level, or something else).
> Warning for invalid appender threshold level never called
> ---------------------------------------------------------
>
> Key: LOG4PHP-162
> URL: https://issues.apache.org/jira/browse/LOG4PHP-162
> Project: Log4php
> Issue Type: Improvement
> Components: Code
> Affects Versions: 2.1
> Reporter: Florian Semm
> Priority: Minor
> Fix For: 2.2
>
>
> appender config:
> <appender name="foo" class="LoggerAppenderConsole" threshold="FOO" />
> Expected warning: "Invalid threshold value [FOO]..."
> LoggerLevel::toLevel() return always level-debug if default-level is null. If
> the threshold unknow the default-level (debug in this case) will be returned.
> There is no need for this warning in line 266-267 LoggerConfigurator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
