You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4php-dev@logging.apache.org by "Christian Hammers (JIRA)" <ji...@apache.org> on 2009/07/26 13:19:14 UTC

[jira] Updated: (LOG4PHP-61) Stick with log4j and allow Logger::getLogger(...)

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

Christian Hammers updated LOG4PHP-61:
-------------------------------------

    Attachment: Logger.diff

be just like log4j

> Stick with log4j and allow Logger::getLogger(...)
> -------------------------------------------------
>
>                 Key: LOG4PHP-61
>                 URL: https://issues.apache.org/jira/browse/LOG4PHP-61
>             Project: Log4php
>          Issue Type: Improvement
>          Components: Code
>    Affects Versions: 2.2
>            Reporter: Christian Hammers
>            Priority: Minor
>         Attachments: Logger.diff
>
>
> Hello
> Both log4j and JDK Logger are suggest using Logger::getLogger() as you can see in:
> http://java.sun.com/j2se/1.4.2/docs/guide/util/logging/overview.html
> http://logging.apache.org/log4j/1.2/manual.html
> I admit that I don't yet understand why there is a LoggerManager class and how it relates to the Logger class but we should try to copy & paste as much as possible from the existing 
> log4j (and log4perl etc) projects. It's log4xxx nevertheless and what would be the benefit from a cross-language standard if we start diversing from it at the very first command :)
> A patch will be attached (I didn't try out if the phpdoc looks good)
> bye,
> -christian-
>  

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