Hi, But that does not work for static loggers. Do you always want to create or lookup one logger per instance?
Gary On Mon, May 9, 2016 at 1:19 PM, Jeff Jensen <[email protected]> wrote: > Perhaps you can use "getClass()" for instance logging? > > For my teams, I make an IDE macro (named "log") that auto-inserts this > line at the cursor: > > private final Logger log = LoggerFactory.getLogger(getClass()); > > > > On Mon, May 9, 2016 at 1:54 PM, Zack Sampson <[email protected]> > wrote: > >> Hey, >> >> >> >> We’ve recently migrated from our own façade around log4j to SLF4J. One of >> the niceties we leave behind is a nullary getLogger call, kind of like so: >> >> >> >> Logger _log = Logger.getLogger(); >> >> >> >> We use reflection to look at the stack and get the calling class’s name. >> We find this more convenient and consistent than manually specifying the >> name of the class. >> >> >> >> Is there any reason SLF4J doesn’t support something like this? >> >> _______________________________________________ >> slf4j-user mailing list >> [email protected] >> http://mailman.qos.ch/mailman/listinfo/slf4j-user >> > > > _______________________________________________ > slf4j-user mailing list > [email protected] > http://mailman.qos.ch/mailman/listinfo/slf4j-user > -- E-Mail: [email protected] | [email protected] Java Persistence with Hibernate, Second Edition <http://www.manning.com/bauer3/> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> Spring Batch in Action <http://www.manning.com/templier/> Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
_______________________________________________ slf4j-user mailing list [email protected] http://mailman.qos.ch/mailman/listinfo/slf4j-user
