[
https://issues.apache.org/jira/browse/LOG4PHP-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840704#action_12840704
]
Christian Grobmeier commented on LOG4PHP-98:
--------------------------------------------
But then you would break your whole application just because somebody
misconfigured logging. I would not like this, having in mind that sometimes
logging configuration is changed on a hot system.
There is a logger hierarhcy available, which defines that "a1.a2" the "a1.a2"
logger gets the configuration of "a1" if there is nothing available for
"a1.a2". I would expect that "L2" would get the configuration of the root
logger in your case
> 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
> Reporter: Florian Platzer
> Priority: Trivial
>
> 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.
