Resend. | -----Original Message----- | From: [EMAIL PROTECTED] | [mailto:[EMAIL PROTECTED]]On Behalf Of Paolo Perego | Sent: Thursday, December 20, 2001 8:57 AM | To: Orion-Interest | Subject: Favourite logging facility survey... | | | Hi orion gurus, I'm taking a look on logging facilities provided by log4j | project and the upcoming Sun jdk1.4. I've, of course, to integrate one of | these facilities in my application deployed with orion. What logging | facilities do you use, if any of course, and which one dao you | think is better between log4j and jdk1.4?
Log4j seems to be fast, feature rich and easy to use. Personally I have used and recommended log4j extensively until ..., well, until someone asked me to write a wrapper for existing logging frameworks. So I took a look into the sources of log4j - and realized that the hierarchical structure behind the scenes is way too complex for most of the projects I was working on. Also the features I have used were just a subset of the full log4j functionality. Unusually a logging framework takes care of system level events and exceptions only - business related events are logged via a different tracking service. In the end people use a logging framework for DEBUG statements during development and ERROR or FATAL for problems during runtime. Therefore log4j seems to be a little bit oversized. So what do I recommend? Log4j is a good and reliable option. But if you need a fast and clean logging framework write your own. 2 classes and one interface are an easy way to start. Or check out protomatter http://protomatter.sourceforge.net/ (See javaworld article for a quick overview). I have never used jdk 1.4 so far ... Jens PS: I run into some issues with the log4j base class Category, which caused "not EJB Spec conform" exceptions (can't remember the correct name) while deploying it into a J2EE server. Not Orion in this case.
