As long as LoggerFactory is a service and not a static singleton like in SLF4J and Log4j2, then the API makes sense in an OSGi context. If it's yet another static factory, then I'd promote the use of Log4j2 instead as we don't need yet another logging facade.
On 6 April 2017 at 12:27, Cristiano Gavião <cvgav...@gmail.com> wrote: > Hello, > I was reading today the early draft of compendium 7.0.0. > > I saw two interfaces that caught my attention: LoggerFactory and Logger. > > could someone explain me the idea behind them? why not importing/extending > interfaces from org.slf4j.api instead? > > If I understood it right, LoggerFactory is aimed to be used as a service, > but I wondering, it would be possible to obtain a Logger from the factory > statically as well as we do when using sfl4j/logback on non-service > classes? > > thanks, > > Cristiano > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev > -- Matt Sicker <boa...@gmail.com>
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
