JAVA PROGRAMMING PITFALLS

By SARAH CLARK

PART ONE THE CLIENT TIER ITEM 1: WHEN RUNTIME EXEC() WON’T ITEM 2: NIO PERFORMANCE AND PITFALLS CANONICAL FILE COPY LITTLE-ENDIAN BYTE OPERATIONS NON-BLOCKING SERVER IO 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! HOW TO USE ASSERTIONS 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 CONTENTS ITEM 13: THE FAILURE TO EXECUTE DEPLOYING JAVA APPLICATIONS THE JAVA EXTENSION MECHANISM SEALED PACKAGES SECURITY ITEM 14: WHAT DO YOU COLLECT? ITEM 15: AVOIDING SINGLETON PITFALLS WHEN MULTIPLE SINGLETONS IN YOUR VM HAPPEN WHEN SINGLETONS ARE USED AS GLOBAL VARIABLES, OR BECOME NON-SINGLETONS ITEM 16: WHEN SETSIZE() WON’T WORK ITEM 17: WHEN POSTING TO A URL WON’T CONNECTING VIA HTTP WITH THE JAVA NET CLASSES AN ALTERNATIVE OPEN SOURCE HTTP CLIENT 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 TWO THE WEB TIER ITEM 23: CACHE, IT’S MONEY ITEM 24: JSP DESIGN ERRORS REQUEST/RESPONSE PARADIGM MAINTAINING STATE JSP THE OLD WAY JSP DEVELOPMENT WITH BEANS (MODEL 1 ARCHITECTURE) JSP DEVELOPMENT IN THE MODEL 2 ARCHITECTURE ITEM 25: WHEN SERVLET HTTPSESSIONS COLLIDE ITEM 26: WHEN APPLETS GO BAD ITEM 27: TRANSACTIONAL LDAP—DON’T MAKE THAT COMMITMENT ITEM 28: PROBLEMS WITH FILTERS ITEM 29: SOME DIRECTION ABOUT JSP REUSE AND CONTENT DELIVERY ITEM 30: FORM VALIDATION USING REGULAR EXPRESSIONS ITEM 31: INSTANCE VARIABLES IN SERVLETS ITEM 32: DESIGN FLAWS WITH CREATING DATABASE CONNECTIONS WITHIN SERVLETS ITEM 33: ATTEMPTING TO USE BOTH OUTPUT MECHANISMS IN SERVLETS ITEM 34: THE MYSTERIOUS FILE PROTOCOL ITEM 35: READING FILES FROM SERVLETS WEB APPLICATION DEPLOYMENT DESCRIPTORS ITEM 36: TOO MANY SUBMITS PREVENTING MULTIPLE SUBMITS HANDLING MULTIPLE SUBMITS PART THREE THE ENTERPRISE TIER ITEM 37: J2EE ARCHITECTURE CONSIDERATIONS ITEM 38: DESIGN STRATEGIES FOR ELIMINATING NETWORK BOTTLENECK PITFALLS A SCENARIO GENERAL DESIGN CONSIDERATIONS EJB DESIGN CONSIDERATIONS ITEM 39: I’LL TAKE THE LOCAL ITEM 40: IMAGE OBSESSION ITEM 41: THE PROBLEM WITH MULTIPLE CONCURRENT RESULT SETS ITEM 42: GENERATING PRIMARY KEYS FOR EJB A SIMPLE SCENARIO A “CLIENT CONTROL” APPROACH THE SINGLETON APPROACH THE NETWORKED SINGLETON APPROACH AN APPLICATION SERVER-SPECIFIC APPROACH DATABASE AUTOGENERATION APPROACHES OTHER APPROACHES ITEM 43: THE STATEFUL STATELESS SESSION BEAN MESSAGE-DRIVEN BEANS ENTITY BEAN STATEFUL SESSION BEAN 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 WHERE’S THE WSDL? ITEM 48: PERFORMANCE PITFALLS IN JAX-RPC APPLICATION CLIENTS EXAMPLE WEB SERVICE A SIMPLE CLIENT THAT USES PRECOMPILED STUB CLASSES A CLIENT THAT USES DYNAMIC PROXIES FOR ACCESS TWO CLIENTS USING THE DYNAMIC INVOCATION INTERFACE (DII) PERFORMANCE RESULTS CONCLUSION ITEM 49: GET YOUR BEANS OFF MY FILESYSTEM! ITEM 50: WHEN TRANSACTIONS GO AWRY, OR CONSISTENT STATE IN STATEFUL SESSION EJBS THE MEMENTO PATTERN