[
https://issues.apache.org/jira/browse/LOG4J2-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13133809#comment-13133809
]
Ralph Goers commented on LOG4J2-37:
-----------------------------------
I understand the bit about separation of the factory from the API and, in fact,
Log4j 2.0 does that. However, that doesn't necessarily lead to the conclusion
that getLogger(Object) is beneficial. Since the configuration is always a
String it hardly seems beneficial to provide an Object just so it can be
converted to a String through hidden magic. In fact, at the moment the Log4j
2.0 API doesn't even provide the getLogger(Class) method since it is just as
easy to do getLogger(Class.getName()) - and under the covers that's all the
implementation does.
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
