J2EE Antipatterns The design patterns we have discussed so far are about learning from what others have done correctly. Skiers, watching the trail from the chairlift above, might point out someone doing a particularly good job getting down the slope. But they always discuss exactly who took a spectacular wipeout and what the hapless victim did to bring it upon themselves. Did he turn a little too fast or put his weight too far back? Antipatterns are to patterns what the falling skier is to the successful one: recurring, sometimes spectacular mistakes that developers make when faced with a common problem.
|Published (Last):||5 August 2010|
|PDF File Size:||1.91 Mb|
|ePub File Size:||14.92 Mb|
|Price:||Free* [*Free Regsitration Required]|
Beschreibungen Titelbeschreibung "The flip-side of Patterns, AntiPatterns provide developers with formal descriptions of common development gaffes that can derail a project along with practical guidelines on how to avoid them.
Each AntiPattern is documented with real-world examples, code, and refactored or escape-route solutions, and the book uses UML where appropriate to diagram improved solutions. Author Bios. Chapter 1: Distribution and Scaling. AntiPattern: Localizing Data. AntiPattern: Misunderstanding Data Requirements.
AntiPattern: Miscalculating Bandwidth Requirements. AntiPattern: Overworked Hubs. AntiPattern: The Man with the Axe. Plan Ahead. Choose the Right Data Architecture. Partition Data and Work. Plan Realistic Network Requirements. Use Specialized Networks.
Be Paranoid. Throw Hardware at the Problem. Chapter 2: Persistence. AntiPattern: Dredge. AntiPattern: Crush. AntiPattern: DataVision. AntiPattern: Stifle. Light Query. Component View. Chapter 3: Service-Based Architecture. AntiPattern: Multiservice. AntiPattern: Tiny Service. AntiPattern: Stovepipe Service. AntiPattern: Client Completes Service. Interface Partitioning. Interface Consolidation. Technical Services Layer. Cross-Tier Refactoring. AntiPattern: Ignoring Reality.
AntiPattern: Too Much Code. AntiPattern: Embedded Navigational Information. Introduce Traffic Cop. Introduce Delegate Controller. Introduce Template. Remove Session Access. Remove Template Text. Introduce Error Page. Chapter 5: Servlets. AntiPattern: Template Text in Servlet. AntiPattern: Not Pooling Connections. AntiPattern: Accessing Entities Directly. Introduce Filters.
Use JDom. Use JSPs. Chapter 6: Entity Beans. AntiPattern: Fragile Links. AntiPattern: Surface Tension. AntiPattern: Coarse Behavior. AntiPattern: Liability. AntiPattern: Mirage. Local Motion. Flat View. Strong Bond. Best of Both Worlds. Chapter 7: Session EJBs. AntiPattern: Sessions A-Plenty. AntiPattern: Bloated Session. AntiPattern: Thin Session. AntiPattern: Large Transaction. AntiPattern: Data Cache. Split Large Transaction. Chapter 8: Message-Driven Beans. AntiPattern: Overloading Destinations.
AntiPattern: Overimplementing Reliability. Architect the Solution. Plan Your Network Data Model. Chapter 9: Web Services. AntiPattern: Single-Schema Dream. RPC to Document Style. Schema Adaptor. Web Service Business Delegate. Chapter J2EE Services. Parameterize Your Solution. Match the Client to the Customer. Control the JNI Boundary. Appendix A AntiPatterns Catalog. Distribution and Scaling AntiPatterns.
Persistence AntiPatterns. Service-Based Architecture AntiPatterns. Servlet AntiPatterns. Entity Bean AntiPatterns. Message-Driven Bean AntiPatterns. Web Services AntiPatterns. Appendix B: Refactorings Catalog. Distribution and Scaling Refactorings.
Persistence Refactorings. Service-Based Architecture Refactorings. Servlet Refactorings. Entity Bean Refactorings. Session EJBs Refactorings. Message-Driven Bean Refactorings.
Web Service Refactorings. J2EE Service Refactorings. System Requirements. He focuses on enterprise integration, Web services, messaging, and service-based architecture.
J2EE Design Patterns by William Crawford, Jonathan Kaplan
Throw Hardware at the Problem. Agreed that it is clunky and inelegant. Request permission to reuse content from this site. Elements of Reusable Object-Oriented Software book, which was the first one in classifying and studying techniques to solve recurring problems in programming, J2EE AntiPatternsrather than listing various design patterns and explaining in what scenarios each one might be applied it is true that some are applicable only when using certain languages or in very specific casesbegins showing the problems that we can face when writing code in an object oriented language like Java, and explains how to solve them by proposing a design pattern.
Explore J2EE Antipatterns
J2EE ANTIPATTERNS PDF