title: Any reason behind "static final Logger" field in singletons classes?
body: <p>We have "private static final" instances of Log4j/commons logging in all service/utility classes (spring singleton beans.) </p>
  
  <p>I am wondering if there is any reasonable case to have those objects "static final" if (1) there are no static methods that use it (2) classes are singletons?</p>
  
  <p>I assume in either static instance or non-static property of a singleton objects - this would be the same old-gen object for JVM. Also I think JVM can easily identify an object if it is private and never changes for any performance purposes (if there are even any). </p>
  
  <p>Is it correct?</p>
  
  <p>Thanks!</p>