Single Submission, Classloaders and Logging, and Unit Test Evangelismby chromatic
ONJava Newsletter for 04/03/2003
Welcome again to the Java newsletter. This week we have three useful and informative articles for your education and entertainment.
With commerce and other business being conducted over the web, transactional integrity is important. In particular, you want to make sure that customers don't accidentally order more refrigerators than they intend if your site is slower than usual. There's no single best solution, be it client- or server-side code. Al Saganich explains potential solutions and their trade-offs in Handling Multiple Submits.
To subscribe to the ONJava.com newsletter (or any O'Reilly Network newsletters), visit https://epoch.oreilly.com/account/default.orm and select the newsletters you wish to receive in your user profile (you'll need to log in with your existing O'Reilly Network account -- if you don't yet have an account, you'll need to create one).
To change your newsletter subscription options, please visit https://epoch.oreilly.com/account/default.orm and click the"Manage My Newsletters" link. For assistance, send help to
Last August, Vikram Goyal examined log4j, the flexible and powerful Java logging package. Much of the feedback asked, "How can I use log4j with J2EE?" It's a little complicated, mostly due to how application servers load classes. In log4j in a J2EE Environment, Vikram explains how classloaders work, and how to deploy log4j to your applications. Even if you don't use J2EE, it's well worth reading just for classloaders.
Finally, Erik M. Burke and Brian M. Coyner, authors of the recently released "Java Extreme Programming Cookbook," have provided a nice piece called Top 12 Reasons to Write Unit Tests. Besides evangelizing the good testing practices XP uses, they briefly examine myths that often lead developers not to write tests. Here's to better software.
An interesting weblog entry passed by today, written by Dalibor Topic. He contributes to the open source Kaffe virtual machine. In particular, the idea that other VMs are already implementing features planned for Java 1.5 is very compelling.
That's all for today. Next week, we'll look at other ways to write PMD rules.
O'Reilly Network Technical Editor
ONJava.com News and Weblogs
Other O'Reilly Network sites
Return to list of ONJava Newsletters.
Return to the ONJava.com.