There might be a problem if you use your own RepositorySelector wich maintains different Repositories depending on some context (MDC etc.). Utility classes whose methods can run in different contexts should fetch the logger each time where it is used. Heri
> -----Original Message----- > From: Jiri Pejchal [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 12, 2008 5:57 PM > To: log4j-user@logging.apache.org > Subject: [SPAM (DNS Blacklist)] - Recommended way of getting > a logger - Sending mail server found on relays.ordb.org > > Hi, > > is there any real difference between getting logger each time > a message is being logged by calling Logger.getLogger() : > > Logger.getLogger(getClass()).info("message"); > > and putting logger as a class member: > final Logger logger = Logger.getLogger(getClass()); > > and than in methods use: > logger.info("message"); > > I have an older web application that uses the first form and > I'm just wondering if I could use the second form without > consequences. > > Thanks. > > Jiri Pejchal > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
