CORE J2EE PATTERNS (BEST PRACTICES AND DESIGN STRATEGIES)
Material type:
TextPublication details: USA PRENTICE HALLISBN: - 0130648841
| Item type | Current library | Call number | Status | Date due | Barcode | |
|---|---|---|---|---|---|---|
| Standard Loan | Thurles Library Main Collection | 005.712 ALU (Browse shelf(Opens below)) | Available | R12074KRCT | ||
| Standard Loan | Thurles Library Main Collection | 005.712 ALU (Browse shelf(Opens below)) | Available | R12072KRCT | ||
| Standard Loan | Thurles Library Main Collection | 005.712 ALU (Browse shelf(Opens below)) | Available | R12076KRCT |
Enhanced descriptions from Syndetics:
Over the last few years, Java 2 Platform, Enterprise Edition (J2EE) technology has emerged and matured as a standard platform for building enterprise applications. While the platform has matured into a solid offering for developing and deploying enterprise applications, it does offer its challenges. As developers, often we confuse learning the technology with learning to design with the technology. In this book, senior architects from the Sun Java Center, Suns Java consulting organization share with the reader their cumulative design experience with and expertise on J2EE technology.The primary focus of the book is on patterns, best practices, design strategies, and proven solutions using the key J2EE technologies including JavaServer Pages (JSP), Servlets, Enterprise Java Beans (EJB), and Java Message Service (J.M.S) API. Other ancillary technologies like JDBC and JNDI are also discussed as relevant to their usage in these patterns. The J2EE Patterns catalog with 16 patterns and numerous strategies is presented to document and promote best practices for these technologies.In addition to the patterns and strategies, the book offers the following: *Presents various design strategies
Table of contents provided by Syndetics
- Foreword
- Preface
- Acknowledgments
- I Patterns and J2ee
- 1 Introduction
- What Is J2EE?
- What Are Patterns?
- Historical References
- Defining a Pattern
- Categorizing Patterns
- J2EE Pattern Catalog
- Continuous Evolution
- How to Use the J2EE Pattern Catalog
- Benefits of Using Patterns
- Patterns, Frameworks, and Reuse
- Summary
- 2 J2EE Platform Overview
- A Brief Perspective
- Application Servers-The New Breed
- Convergence of Java Technologies
- The Rise of the J2EE Platform
- J2EE Value Proposition
- J2EE Platform
- J2EE Architecture
- Java 2 Standard Edition
- J2EE Application Components and Containers
- Standard Services
- J2EE Platform Roles
- Deployment Descriptors
- J2EE Patterns and J2EE Platform
- Summary
- II Design Considerations, Bad Practices, and Refactorings
- 3 Presentation Tier Design Considerations and Bad Practices
- Presentation Tier Design Considerations
- Session Management
- Controlling Client Access
- Validation
- Helper Properties-Integrity and Consistency
- Presentation Tier Bad Practices
- Control Code in Multiple Views
- Exposing Presentation-Tier Data Structures to Business Tier
- Exposing Presentation-Tier Data Structures to Domain Objects
- Allowing Duplicate Form Submissions
- Exposing Sensitive Resources to Direct Client Access
- Assuming
- Will Reset Bean Properties
- Creating Fat Controllers
- 4 Business Tier Design Considerations and Bad Practices
- Business Tier Design Considerations
- Using Session Beans
- Using Entity Beans
- Caching Enterprise Bean Remote References and Handles
- Business and Integration Tiers Bad Practices
- Mapping Object Model Directly to Entity Bean Model
- Mapping Relational Model Directly to Entity Bean Model
- Mapping Each Use Case to a Session Bean
- Exposing All Enterprise Bean Attributes via Getter/Setter Methods
- Embedding Service Lookup in Clients
- Using Entity Bean as Read-Only Object
- Using Entity Beans as Fine-Grained Objects
- Storing Entire Entity Bean-Dependent Object Graph
- Exposing EJB-related Exceptions to Non-EJB Clients
- Using Entity Bean Finder Methods to Return a Large Results Set
- Client Aggregates Data from Business Components
- Using Enterprise Beans for Long-Lived Transactions
- Stateless Session Bean Reconstructs Conversational State for Each Invocation
- 5 J2EE Refactorings
- Presentation Tier Refactorings
- Introduce a Controller
- Introduce Synchronizer Token
- Localize Disparate Logic
- Hide Presentation Tier-Specific Details From the Business Tier
- Remove Conversions from View
- Hide Resource From a Client
- Business and Integration Tier Refactorings
- Wrap Entities With Session
- Introduce Business Delegate
- Merge Session Beans
- Eliminate Inter-Entity Bean Communication
- Move Business Logic to Session
- General Refactorings
- Separate Data Access Code
- Refactor Architecture by Tiers
- Use A Connection Pool
- III J2EE Pattern Catalog
- 6 J2EE Patterns Overview
- What Is a Pattern? Identifying a Pattern
- The Tiered Approach
- J2EE Patterns
- Presentation Tier Patterns
- Business Tier Patterns
- Integration Tier Patterns
- Guide to the Catalog
- Terminology
- Use of UML
- Pattern Template
- J2EE Pattern Relationships
- Relationship to Known Patterns
- Patterns Roadmap
- Summary
- 7 Presentation Tier Patterns
- Intercepting Filter
- Context
- Problem
- Forces
- Solution
- Consequences
- Related Patterns
- Front Controller
- Context
- Problem
- Forces
- Solution
- Consequences
- Related Patterns
- View Helper
- Context
- Problem
- Forces
- Solution
- Consequences
- Related Patterns
- Composite View
- Context
- Problem
- Forces
- Solution
- Consequences
- Sample Code
- Related Patterns
- Service to Worker
- Context
- Problem
- Forces
- Solution
- Consequences
- Sample Code
- Related Patterns
- Dispatcher View
- Context
- Problem
- Forces
- Solution
- Consequences
- Sample Code
- Related Patterns
- 8 Business Tier Patterns
- Business Delegate
- Context
- Problem
- Forces
- Solution
- Consequences
- Sample Code
- Related Patterns
- Value Object
- Context
- Problem
- Forces
- Solution
- Consequences
- Sample Code
- Related Patterns
- Session Facade
- Context
- Problem
- Forces
- Solution
- Consequences
- Sample Code
- Related Patterns
- Composite Entity
- Context
- Problem
- Forces
- Solution
- Consequences
- Sample Code
- Related Patterns
- Value Object Assembler
- Context
- Problem
- Forces
- Solution
- Consequences
- Sample Code
- Related Patterns
- Value List Handler
- Context
- Problem
- Forces
- Solution
- Consequences
- Sample Code
- Related Patterns
- Service Locator
- Context
- Problem
- Forces
- Solution
- Consequences
- Sample Code
- Related Patterns
- 9 Integration Tier Patterns
- Data Access Object
- Context
- Problem
- Forces
- Solution
- Consequences
- Sample Code
- Related Patterns
- Service Activator
- Context
- Problem
- Forces
- Solution
- Consequences
- Sample Code
- Related Patterns
- EPILOGUE J2EE Patterns Applied
- PSA Overview
- Use Case Model
- Use Cases, Patterns, and Pattern Frameworks
- Create Project Use Case
- Pattern Identification
- Pattern Realization
- Reserve Resource Use Case
- Pattern Identification
- Pattern Realization
- Find Available Resources Use Case
- Pattern Identification
- Pattern Realization
- Bibliography
- Apache Software License
- Index
Author notes provided by Syndetics
DEEPAK ALUR is an Enterprise Java Architect with the Sun Java Center. He has over 12 years of experience in the software industry. He has been focused on design and implementation of enterprise applications using Object-Oriented technologies, patterns, Java, and J2EE.
JOHN CRUPI is the Chief Java Architect of the Sun Java Center. He has over 15 years of experience in distributed object computing and remains focused on creating reusable, scalable architectures for J2EE. He is also a JavaReport columnist for the Architect's Corner.
DAN MALKS is an Enterprise Java Architect with the Sun Java Center. He has over 14 years of experience in the software industry and focuses on Object-Oriented technologies. He has been published in numerous industry periodicals and books on Java, J2EE, and patterns.