> On Aug 14, 2017, at 11:49 AM, Gary Gregory <[email protected]> wrote: > > On Mon, Aug 14, 2017 at 12:35 PM, Gary Gregory <[email protected]> > wrote: > >> Probably for Ralph: >> >> Right now, it's the LogManager in log4j-api that converts Class names into >> Logger names. >> >> There is no getLogger(Class) API in the Core LoggerContext. >> >> Should we push down this conversion into Core's LoggerContext? >> >> It seems the sane thing to do to: >> - Avoid making something pluggable in log4j-api >> - Avoid making Core parse logger names looking for separators. >> > > But that would mean adding two methods to: > > org.apache.logging.log4j.spi.LoggerContext: > > org.apache.logging.log4j.spi.LoggerContext.getLogger(Class<?>) > org.apache.logging.log4j.spi.LoggerContext.getLogger(Class<?>, > MessageFactory) > > Thoughts? >
Why does it mean that? Ralph
