[
https://issues.apache.org/jira/browse/LOG4PHP-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13639105#comment-13639105
]
fseidenschwan commented on LOG4PHP-188:
---------------------------------------
I'm using Release 2.3.0 now and I think fixing this "Bug" was a mistake.
Comming from log4j, I know it possible, even WANTED to provide the possiblity to
allow a depper log level for child loggers!
e.g.:
<root>
<level value="info" />
<appender_ref ref="RollingFileAppender" />
<appender_ref ref="FatalRollingFileAppender" />
</root>
So any logger dynamically created by Logger::getLogger( name )
will "inherit" these two appenders.
The trouble is the created loggers do not have appenders on their own but only
the ones of their parents.
Using API calls to set the logger level is pointless with the current
implementation. (-_-)
Shouldn't log4php be similiar to log4j in usage and API?
> rootLogger logs although level isn't reached
> --------------------------------------------
>
> Key: LOG4PHP-188
> URL: https://issues.apache.org/jira/browse/LOG4PHP-188
> Project: Log4php
> Issue Type: Bug
> Components: Code
> Affects Versions: 2.2.1
> Environment: Windows Server 2008 R2, IIS 7
> Reporter: Florian Platzer
> Assignee: Ivan Habunek
> Fix For: 2.2.1
>
> Attachments: log4php.patch, test.php
>
>
> I downloaded the current version of log4php and used an existing
> configuration:
> rootLogger (level = FATAL, appender = echo)
> customLog (level = DEBUG, appender = dailyfile)
> When i log to customLog with DEBUG level, i also get the message printed on
> screen:
> Logger::getLogger('customLog')->debug('test');
> When I change rootLogger's appender to dailyfile, the message is logged twice
> in the log file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
