[jira] Resolved: (LOG4PHP-67) Refactoring: Use Logger instead of LoggerManager

["Christian Grobmeier (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LOG4PHP-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Grobmeier resolved LOG4PHP-67.
----------------------------------------

    Resolution: Fixed

Committed with rv800094

> Refactoring: Use Logger instead of LoggerManager
> ------------------------------------------------
>
>                 Key: LOG4PHP-67
>                 URL: https://issues.apache.org/jira/browse/LOG4PHP-67
>             Project: Log4php
>          Issue Type: Improvement
>          Components: Code
>            Reporter: Christian Grobmeier
>             Fix For: 2.0
>
>
> Reading: http://logging.apache.org/log4j/1.2/manual.html
> While Log4PHP is always speaking of LoggerManager::getLogger, Log4J
> uses: Logger.getLogger.
> There is actually a LogManager class available in Log4J, but I couldn't
> find any reference from the documentation to it. I guess it's the
> preferred way of Log4J to use Logger.getLogger().
> In Log4php you can currently use Logger class to retrieve a logger. Is
> redirecting this request to the loggerManager, which returns the
> LoggerHierarchy which returns the actual logger.
> You can also use the LoggerManager directly to retrieve a Logger.
> This is confusing. What should one use? Why two ways? I hardly see a
> benefit in having the LoggerManager class. Its just defining the
> classloader and references to the LoggerHierarchy.
> As discussed on the mailinglist, LoggerManager should be removed and Logger class
> should be used instead.

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