O’Reilly has an article on using the Java 1.4 logging API. It doesn’t answer the burning question, though, which is how the API compares to Log4j, which is pretty nice in its own right. It’s unfortunate that the API described in the article isn’t a drop-in replacement for Log4j, because from the looks off things, the two are very similar. The nicest feature of Log4j is that you can throw a config file for Log4j into your classpath and it will be picked up automatically. In each environment I use, I have a customized Log4j properties file … that makes it easy to keep heavy duty logging enabled on my desktop machine, slightly lesser logging in development, and only logging of errors turned on in production.
Using the Java 1.4 logging API
O’Reilly has an article on using the Java 1.4 logging API. It doesn’t answer the burning question, though, which is how the API compares to Log4j, which is pretty nice in its own right. It’s unfortunate that the API described in the article isn’t a drop-in replacement for Log4j, because from the looks off things, the two are very similar. The nicest feature of Log4j is that you can throw a config file for Log4j into your classpath and it will be picked up automatically. In each environment I use, I have a customized Log4j properties file … that makes it easy to keep heavy duty logging enabled on my desktop machine, slightly lesser logging in development, and only logging of errors turned on in production.
Commentary
Previous post
Mandrake available at Wal-MartNext post
Israel and Palestine again