Win a copy of Five Lines of Code this week in the OO, Patterns, UML and Refactoring forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

About Log4J hierarchy question

 
Ranch Hand
Posts: 220
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Dear all,
I am going to reading the document of Log4J. However, I have a very basic question that I don't understand.
What is the uses of Logger Hierachy? It seems the document doesn't mention the uses of the hierarchy. Actually, logger is just an object with a name associated on it. I really don't understand why use hierarchy.
Please help
Thanks
Benson
 
Ranch Hand
Posts: 47
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The advantage of the Logger hierarchy is the granularity of logging that can be achieved.
Logging verbosity may be controlled either at the high level or the low level as the levels are loosely coupled and new levels can easily be added at a later date. If lots of control is not required over the logging in your application, you can manage with just the root logger. On the other hand you can delve as deep and as detailed as you like. Hope that helps.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
    Bookmark Topic Watch Topic
  • New Topic