[jira] Commented: (LOG4PHP-98) Check for invalid names on getLogger call

["Moritz Schmidt (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LOG4PHP-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12891543#action_12891543 ] 

Moritz Schmidt commented on LOG4PHP-98:
---------------------------------------

We name our loggers often like 'project.component.class' . 
Thus, very many loggers are used, but we actually configure only a handful as needed (sometimes changing the logging configuration on a production system to get only some specific classes' messages). 

Now, if every non-configured logger complained, we'd have a problem ;)


What about having a flag like Logger::$warnNotConfigured (boolean, false per default) that will cause a concrete logger to produce a notice/echo/error_log if it has no appenders?

> Check for invalid names on getLogger call
> -----------------------------------------
>
>                 Key: LOG4PHP-98
>                 URL: https://issues.apache.org/jira/browse/LOG4PHP-98
>             Project: Log4php
>          Issue Type: Improvement
>          Components: Code
>    Affects Versions: 2.0
>            Reporter: Florian Platzer
>            Priority: Trivial
>             Fix For: 2.1
>
>
> When calling the Logger::getLogger function a name-check would be helpful.
> So, if someone defines the logger "L1" and calls $_logger = Logger::getLogger('L2'); an exception could be thrown

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.