Table of content
|
Expert One-on-One J2EE Design and Development Authors: Johnson R. Published year: 2005 Pages: 1/183 |
 |
- Table of Contents
- Table of Contents
- BackCover
- Expert One-on-One J2EE Design and Development
- Introduction
- How is this Book Different?
- Who this Book is for
- Aims of this Book
- What this Book Covers
- Assumed Knowledge
- Recommended Reading
- What You Need for Using this Book
- Conventions
- Customer Support
- How to Download the Sample Code for the Book
- Errata
- E-Mail Support
- p2p.wrox.com
- Chapter 1: J2EE Architectures
- Goals of an Enterprise Architecture
- Deciding Whether to Use a Distributed Architecture
- New Considerations in J2EE Design
- When to Use EJB
- Accessing Data
- State Management
- J2EE Architectures
- Web Tier Design
- Designing Applications for Portability
- Summary
- Chapter 2: J2EE Projects--Choices and Risks
- Developing a Policy on Specification Versions
- Choosing an Application Server
- The Neat Technology Trap
- When to Use Alternative Technologies to Supplement J2EE
- Portability Issues
- Staging Environments and Release Management
- Building a Team
- Choosing Development Tools
- Identifying and Mitigating Risks
- Summary
- Chapter 3: Testing J2EE Applications
- What Can Testing Achieve?
- Definitions
- Testing Correctness
- Testing Performance and Scalability
- Automating Tests
- Complementary Approaches to Testing
- Summary
- Chapter 4: Design Techniques and Coding Standards for J2EE Projects
- OO Design Recommendations for J2EE Applications
- Coding Standards
- Why (and How) Not to Reinvent the Wheel
- Summary
- Chapter 5: Requirements for the Sample Application
- Overview
- User Populations
- Assumptions
- Scope Limitations
- Delivery Schedule
- Internet User Interface
- Box Office User Interface
- Non-Functional Requirements
- Hardware and Software Environment
- Summary
- Chapter 6: Applying J2EE Technologies
- When is a Distributed Architecture Appropriate?
- Deciding When to Use EJB
- Deciding How to Use EJB
- Deciding when to Use Asynchronous Calling with JMS
- Authentication and Authorization
- Deciding When to Use XML
- Caching to Improve Performance
- Summary
- Chapter 7: Data Access in J2EE Applications
- Data Access Goals
- Business Logic and Persistence Logic
- Object-Driven and Database-Driven Modeling: A Philosophical Debate
- OR Mapping and the Impedance Mismatch
- The Data Access Object (DAO) Pattern
- Working with Relational Databases
|
Expert One-on-One J2EE Design and Development Authors: Johnson R. Published year: 2005 Pages: 1/183 |
|