You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2012/09/17 07:49:07 UTC

[jira] [Closed] (LOG4J2-37) Support getLogger(Object)

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

Ralph Goers closed LOG4J2-37.
-----------------------------

    Resolution: Won't Fix

As an update to my previous comment, getLogger does now support accepting a Class. However, anything beyond that seems unnecessary and problematic. Maintaining the Logger hierarchy when the "names" are arbitrary Objects seems unworkable. Further, no other logging framework I'm aware of allows this.
                
> Support getLogger(Object)
> -------------------------
>
>                 Key: LOG4J2-37
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-37
>             Project: Log4j 2
>          Issue Type: Task
>          Components: API
>            Reporter: Curt Arnold
>
> Suggested at http://wiki.apache.org/commons/Logging/ConfigurationAndDiscovery

--
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

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org