Comments on: Static v Non-static loggers

By: Sam Newman

Sam Newman — Fri, 05 Sep 2003 04:14:00 +0000

Instance-specific loggers do have a place, where their very individuality imparts on the nature of the logging. To take a trivial example, imagine an instance specific logger used in a User class. Here, all messages logged could automatically log user information along with the messages. This might of course be overkill, but you get my point I hope :-) That said, I’ve never yet needed to use an object-level logger!

By: ade

ade — Sun, 22 Jun 2003 03:54:00 +0000

Try this variation on the template idea instead:
private static final Logger log = Logger.getLogger(”${enclosing_package}.${enclosing_type}”);
The difference is that your loggers end up using the fully qualified name.

By: Ryan Breidenbach

Ryan Breidenbach — Thu, 19 Jun 2003 21:01:00 +0000

Greg - I hope you are joking about that stack trace parsing ;-) Yuck!
Here, we use Eclipse and we just added a Template to cover this: Preferences -> Java -> Editor -> Templates. We created one with the name “logger” and pattern “private static final Logger LOGGER = Logger.getLogger(${enclosing_type}.class);” Now, any time we want to add a logger to a class, we just type logger and hit Ctrl + Space and viola! Most decent IDEs will let you do this.
Ryan