4 of 4 people found the following review helpful:
5.0 out of 5 stars
Good resource, very relevant to problem solving, May 12, 2003
This review is from: More Java Pitfalls: 50 New Time-Saving Solutions and Workarounds (Paperback)
This book is full of valuable information, and something that I believe I can use for my team of Java developers on our projects. I have enjoyed this entire book, but here are my comments on a few of my favorite "articles" from this book.
#1 - When Runtime.exec() won't. An excellent 13 page discussion of how things can go wrong with the famous Runtime.exec(). There are so many ways to mess up when running OS processes from Java, and this article discusses most of them, and more importantly, the right way to go about using Runtime.exec().
#5 - Avoid Granularity Pitfalls in java.util.logging. This is a well-written discussion of the java.util.logging API, and helps programmers avoid using it in the wrong way. This is a good tutorial, but I really like the pictures that show the relationship between the logger and the handler - it is much easier for people to understand that way.
#15 - Avoiding singleton pitfalls - This is a great discussion of how multiple "singletons" can happen in your VM, if you don't set them up the right way... My company has seen this happen a lot, but I have seen few discussions on it before this book.
#24 - JSP design errors. This is something that I don't believe many other books talk about, and is very valuable. A lot of the JSPs that I have seen out there look bad, and this shows how they should be developed. The examples are good, and this is short and to the point and conveys the points well.
#41 - The problem with multiple concurrent ResultSets. This shows an example of having 2 ResultSet objects open at the same time in an iteration, and showing the results in Sybase, Oracle, MySQL, Access, and SQLServer. It shows how, depending on the implementation of the driver & database, different behavior can be seen, and shows how to fix it. This is an excellent article - most examples I have seen before do not take the time to show behavior from multiple databases.
These are only a few of the articles from this book. I like the book because it is full of self-contained articles that discuss aspects of the Java programming language that are tricky - or are often misunderstood and misused. I also like it because it covers performance, design, and in many cases, gives metrics. Some of the APIs discussed in the book I have not used yet (j2me, jaxrpc, jaxr), but probably will in the future. This is an extremely relevant resources.
I can't say enough good things about this book. I give this an excellent rating, and recommend it highly.
Help other customers find the most helpful reviews
Was this review helpful to you? Yes
No
4 of 4 people found the following review helpful:
5.0 out of 5 stars
A Top Shelf Java Resource, April 21, 2003
This review is from: More Java Pitfalls: 50 New Time-Saving Solutions and Workarounds (Paperback)
After reading this book, I am certain that it will serve as a tremendous resource to both the programmer and architect alike. Each pitfall gives the developer practical advise through the use of concise and effective examples. The architect receives accurate and honest tradeoffs and evaluations of all viable options to be considered, along with a valid recommendation and rationale. This book should serve as a "top shelf" reference for all developers who take seriously the business of crafting quality Java-based software solutions.
Help other customers find the most helpful reviews
Was this review helpful to you? Yes
No
4 of 4 people found the following review helpful:
5.0 out of 5 stars
Like Everything but the title, April 17, 2003
This review is from: More Java Pitfalls: 50 New Time-Saving Solutions and Workarounds (Paperback)
This is a wonderful book, and I have already used it to fix problems. I highly recommend it. Like the source code, like the examples, and like the solutions.
Help other customers find the most helpful reviews
Was this review helpful to you? Yes
No