More Java Pitfalls
50 New Time-Saving Solutions and Workarounds
Published on 10. March 2003
480 pages
978-0-471-46724-3 (ISBN)
Description
* Building on the success of Java Pitfalls (0-471-36174-7), thisbook provides more specific programming solutions to fiftydifficult Java programming problems
* Shows experienced programmers how to identify and avoidweaknesses in Java and related J2EE technologies that can causeprograms to go haywire
* Explores advanced topics including networking, XML and Javaprogramming, and the Java Virtual Machine
More details
Other editions
Additional editions
Michael C. Daconta | Kevin B. Smith | Donald Avondolio
More Java Pitfalls
50 New Time-Saving Solutions and Workarounds
Book
03/2003
1st Edition
Wiley
€38.90
Article exhausted; check different version
Persons
MICHAEL C. DACONTA is Director of Web and Technology Services forMcDonald Bradley, Inc., where he develops advanced Java systems. Heis the author of numerous programming books on C, C++, Java, andXML.
KEVIN T. SMITH is a Principal Software Architect at McDonaldBradley, Inc., where he develops Java-based Internet securitysolutions.
DONALD AVONDOLIO is a Senior Architect/Developer at McDonaldBradley, Inc.
W. CLAY RICHARDSON is a Senior Architect/Developer at McDonaldBradley, Inc., where he currently serves as a development teamlead.
Content
Introduction.
Acknowledgments.
PART ONE. THE CLIENT TIER.
Item 1. When Runtime.exec( ) won't.
Item 2. NIO Performance and Pitfalls.
Item 3. I Prefer Not to Use Properties.
Item 4. When Information Hiding Hides Too Much.
Item 5. Avoiding Granularity Pitfalls in java.util.logging.
Item 6. When Implementations of Standard APIs Collide.
Item 7. My Assertions are Not Gratuitous!
Item 8. The Wrong Way to Search a DOM.
Item 9. The Saving a DOM Dilemma.
Item 10. Mouse Button Portability.
Item 11. Apache Ant and Lifecycle Management.
Item 12. JUnit: Unit Testing Made Simple.
Item 13. The Failure to Execute.
Item 14. What Do You Collect?
Item 15. Avoiding Singleton Pitfalls.
Item 16. When setSize( ) Won't Work.
Item 17. When Posting to a URL Won't.
Item 18. Effective String Tokenizing.
Item 19. Jlayered Pane Pitfalls.
Item 20. When File.renameTo( ) Won't.
Item 21. Use Iteration over Enumeration.
Item 22. J2ME Performance and Pitfalls.
PART T WO. THE WEB TIER.
Item 23. Cache, It's Money.
Item 24. JSP Design Errors.
Item 25. When Serlet HttpSessions Collide.
Item 26. When Applets Go Bad.
Item 27. Transactional LDAP - Don't Make the Commitment.
Item 28. Filtered Java: It's Smooth.
Item 29. Some Direction about JSP Reuse and ContentDelivery.
Item 30. I'll Take my Java Regular.
Item 31. Instance Variables In Servlets.
Item 32. Design Flaws with Creating Database Connections WithinServlets.
Item 33. Attempting to Use Both Output Mechanisms inServlets.
Item 34. The Mysterious File Protocol.
Item 35. Reading Files from Servlets.
Item 36. Too Many Submits.
PART THREE. THE ENTERPRISE TIERS.
Item 37. J2EE Architecture Considerations.
Item 38. Design Strategies for Eliminating Network BottleneckPitfalls.
Item 39. I'll Take the Local.
Item 40. Image Obsession.
Item 41. The Problem with Multiple Concurrent ResultSets.
Item 42. Generating Primary Keys for EJB.
Item 43. The Stateful Stateless Session Bean.
Item 44. The Unprepared PreparedStatement.
Item 45. Take a Dip in the resource Pool.
Item 46. JDO and Data Persistence.
Item 47. Where's the WSDL? Pitfalls of Using JAXR with UDDI.
Item 48. Performance Pitfalls in JAX-RPC ApplicationClients.
Item 49. Get Your Beans Off My Filesysem!
Item 50. When Transactions Go Away, or Consistent State inStateful Session EJBs.
Index.
