This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
They tell you that Log4J support JDK 1.1.x but it's not so, I have problem to run it under something lower than 1.2 because it's using JavaBeans with some definitions exist only since 1.2 Beside that it's just *excellent* product and I enjoy it a lot.
Joined: Jan 08, 2002
Have not done any complex customization. There is a file called log4j_conf.properties where you can provide your own configuration parameters. When you are logging be sure to pay attention to the different levels of logging ie. debug, info, error etc. as you can turn these on and off inside the properties file w/o actually deleting the log statement from the code. It comes in handy when you take the code into a production environment. Michael
Hi, I have used LOG4J for my last project and I loved it and will recommend it to any one. In fact Sun's upcoming logging API is a lighter version of LOG4J. It gives you full control over the logging by a using a configuration file in XML or Java properties file format. And it allows you to log to different appenders for example System.out, File , Database, NTEventLog and also allows you to develop your own appenders. For example in my last project I used the JDBCAppender to log to a database and developed my own Appender to log messages to TIB/Hawk in real time. BTW, TIB/Hawk is a Monitoring Application in TIBCO's(one of the major EAI software vendor) Active Enterprise product suite. And I developed a wrapper API on top of LOG4J API to be used by the other modules in the project. And it was loved by everyone in the project. If someone needs any help I am willing to share my knowledge. Thks Vignes Inpanathan
Hi Vignes, With the upcoming release of J2SE1.4(It's in release candidate phase) could you please highlight the signficant differences between Log4J and the logging API. I do know that the logging API will not work with earlier versions of J2SE. Other than that can you tell us any differences between the 2 API's which can cause an impact on an Application's logging capabilities. I have had a look at both and it's quite obvious that the logging API is highly 'influenced' by Log4J and has borrowed heavily from it. It's usually easier to get buy in from management/developers to use an API that's part of the Standard package. Is there any compelling reason where I can say that Log4j will be better? Thanks Ravi
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com