Wonder Club world wonders pyramid logo
×

Expert One-on-One J2EE Design and Development Book

Expert One-on-One J2EE Design and Development
Expert One-on-One J2EE Design and Development, What is this book about?
The results of using J2EE in practice are often disappointing: applications are often slow, unduly complex, and take too long to develop. Rod Johnson believes that the problem lies not in J2EE itself, but in that it is often, Expert One-on-One J2EE Design and Development has a rating of 3.5 stars
   2 Ratings
X
Expert One-on-One J2EE Design and Development, What is this book about? The results of using J2EE in practice are often disappointing: applications are often slow, unduly complex, and take too long to develop. Rod Johnson believes that the problem lies not in J2EE itself, but in that it is often, Expert One-on-One J2EE Design and Development
3.5 out of 5 stars based on 2 reviews
5
0 %
4
50 %
3
50 %
2
0 %
1
0 %
Digital Copy
PDF format
1 available   for $99.99
Original Magazine
Physical Format

Sold Out

  • Expert One-on-One J2EE Design and Development
  • Written by author Rod Johnson
  • Published by Wiley, John & Sons, Incorporated, October 2002
  • What is this book about? The results of using J2EE in practice are often disappointing: applications are often slow, unduly complex, and take too long to develop. Rod Johnson believes that the problem lies not in J2EE itself, but in that it is often
  • This guide to J2EE focuses on solving common problems and avoiding debilitating mistakes. Johnson (a Java architect) examines the complexities of J2EE services and advocates the simplest possible solutions. Specific instructions are offered for using dist
Buy Digital  USD$99.99

WonderClub View Cart Button

WonderClub Add to Inventory Button
WonderClub Add to Wishlist Button
WonderClub Add to Collection Button

Book Categories

Authors

Introduction1
J2EE Myths2
How is this Book Different?5
My Approach6
Who this Book is for7
Aims of this Book7
What this Book Covers7
Assumed Knowledge8
Recommended Reading9
What You Need to Use this Book9
Chapter 1J2EE Architectures15
Goals of an Enterprise Architecture16
Deciding Whether to Use a Distributed Architecture18
New Considerations in J2EE Design19
When to Use EJB20
Implications ofUsing EJB20
Questionable Arguments for Using EJB22
Compelling Arguments for Using EJB22
Arguments for Using EJB to Consider on a Case-by-Case Basis23
Accessing Data24
J2EE Data Access Shibboleths24
State Management26
J2EE Architectures26
Common Concepts27
Non-distributed Architectures28
Distributed Architectures32
Web Tier Design36
The Model View Controller (MVC) Architectural Pattern36
Connectivity Between the Web Tier and Business Objects38
Designing Applications for Portability38
Summary40
Chapter 2J2EE Projects: Choices and Risks43
Developing a Policy on Specification Versions44
Choosing an Application Server45
When to Choose an Application Server46
Defining the Requirements47
Evaluation Criteria48
Choice Process54
Top Mistakes in Choosing an Application Server54
The "Neat Technology" Trap55
When to Use Alternative Technologies to Supplement J2EE56
Portability Issues56
What does Portability Mean?57
A Pragmatic Approach to Portability58
Staging Environments and Release Management58
Building a Team60
Team Structure60
Choosing Development Tools63
Visual Modeling Tools64
IDEs64
Build Utilities64
Code Generators66
Version Control67
Identifying and Mitigating Risks67
Summary71
Chapter 3Testing J2EE Applications73
What Can Testing Achieve?74
Definitions75
Testing Correctness76
The XP Approach to Testing76
Writing Test Cases78
Unit Testing78
Should Testing Strategy Affect How We Write Code?90
Integration and Acceptance Testing92
Testing Business Objects92
Testing Web Interfaces100
Design Implications105
Testing Performance and Scalability105
Load Testing EJBs and Other Business Objects106
Load Testing Web Interfaces107
Automating Tests107
Complementary Approaches to Testing108
Summary110
Chapter 4Design Techniques and Coding Standards for J2EE Projects113
00 Design Recommendations for J2EE Applications114
Achieving Loose Coupling with Interfaces115
Prefer Object Composition to Concrete Inheritance115
The Template Method Design Pattern117
The Strategy Design Pattern119
Using Callbacks to Achieve Extensibility120
The Observer Design Pattern122
Consider Consolidating Method Parameters124
Exception Handling--Checked or Unchecked Exceptions125
Using Reflection132
Using JavaBeans to Achieve Flexibility138
Avoid a Proliferation of Singletons by Using an Application Registry139
Refactoring142
Coding Standards142
Start from the Standard143
Allocation of Responsibilities145
Avoid Code Duplication146
Avoid Literal Constants147
Visibility and Scoping149
Using the final Keyword153
Implementing toString() Methods Useful for Diagnostics155
Defensive Coding Practices156
Prefer Arrays to Collections in Public Method Signatures157
Documenting Code158
Logging160
Why (and How) Not to Reinvent the Wheel166
Help! API Overload167
Using Frameworks167
Summary171
Chapter 5Requirements for the Sample Application179
Overview180
User Populations180
Public Internet Users180
Box Office Users181
Administrators182
Assumptions182
Scope Limitations183
Delivery Schedule183
Internet User Interface183
Basic Workflow184
Error Handling185
Application Screens185
Box Office User Interface198
Non-Functional Requirements198
Hardware and Software Environment199
Summary200
Chapter 6Applying J2EE Technologies203
When is a Distributed Architecture Appropriate?204
Distributed Applications and Scalability205
Distributed Applications and Reliability206
Scalable and Robust Architectures207
High-level Architecture for the Sample Application209
Deciding When to Use EJB209
Using EJB to Implement a Distributed Architecture209
Transaction Management210
EJB and Authorization213
EJB and Multi-threading214
Declarative Configuration Management214
The Downside of EJB214
EJBs in the Sample Application222
Deciding How to Use EJB223
What Should EJBs Do?223
When to Use Local or Remote Interfaces223
Using EJBs in the Sample Application227
Deciding when to use Asynchronous Calling with JMS228
Message-Oriented Middleware (MOM) and JMS228
Producing Messages228
Consuming Messages229
When to Use Asynchronous Calling232
JMS in the Sample Application234
Authentication and Authorization235
The Standard Security Infrastructure235
The Server Implementation237
Deciding When to Use XML238
Using XSLT in J2EE Applications238
"Deep" Use of XML239
Converting Between JavaBeans and XML241
J2EE and XML in the Future244
XML in the Sample Application245
Caching to Improve Performance245
Caching Options245
A Caching Strategy for the Sample Application247
Summary248
Chapter 7Data Access in J2EE Applications251
Data Access Goals252
Business Logic and Persistence Logic252
Object-Driven and Database-Driven Modeling: A Philosophical Debate253
O/R Mapping and the "Impedance Mismatch"255
The Data Access Object (DAO) Pattern257
Working with Relational Databases259
Referential Integrity259
Stored Procedures, Triggers, and Views259
RDBMS Performance Issues262
Portability Versus Performance263
Exchanging Data in Distributed Applications265
The Value Object J2EE Pattern265
"Generic" Value Objects267
"Disconnected" Data Access Using JDBC Rowsets267
Common Data Access Issues268
Transaction Isolation268
Pessimistic and Optimistic Locking269
Primary Key Generation Strategies269
Where to Perform Data Access273
Data Access in the EJB Tier273
Data Access in the Middle Tier without Using EJB275
Data Access in the Web Tier276
Summary278
Data Modeling in the Sample Application278
Chapter 8Data Access Using Entity Beans285
Entity Bean Concepts286
Definition287
How Should We Use Entity Beans?288
CMP Versus BMP292
Entity Beans in EJB 2.0294
Local Interfaces294
Home Interface Business Methods295
EJB 2.0 CMP296
Entity Bean Caching300
Entity Bean Locking Strategies301
Read-only and "Read-mostly" Entities302
Transactional Entity Caching304
Entity Bean Performance305
Tool Support for Entity Beans306
Summary306
Chapter 9Practical Data Access311
Data Access Technology Choices312
SQL-Based Technologies312
O/R Mapping Technologies315
Choosing a Data Access Strategy for the Sample Application319
JDBC Subtleties320
Correct Exception Handling320
Extracting Information from SQLExceptions322
The PreparedStatement Question323
A Generic JDBC Abstraction Framework324
Motivation325
Aims326
Exception Handling327
Two Levels of Abstraction333
A Framework to Control JDBC Workflow and Error Handling333
A Higher Level of Abstraction: Modeling RDBMS Operations as Java Objects342
JDBC Abstraction Summary351
Implementing the DAO Pattern In the Sample Application353
Summary360
Chapter 10Session Beans363
Using Stateless Session Beans364
Benefits of Stateless Session Beans364
Stateless Session Beans and Internal State365
Implications of Stateless Session Bean Pooling365
Using Stateful Session Beans366
Why Not to Use Stateful Session Beans366
When to Use Stateful Session Beans370
Session Synchronization370
Protecting Stateful Session Beans from Concurrent Calls371
Patterns for Achieving Stateful Functionality with SLSBs371
Using a Stateful Session Bean as Controller373
J2EE Design Patterns Applicable to Session Beans373
The Session Facade Pattern in Distributed J2EE Applications374
The EJB Command Design Pattern374
Session Bean Implementation Issues379
Error Handling in EJBs379
Transaction Attributes for EJBs using CMT382
The Business Methods Interface "Pattern"386
Session Beans in the Sample Application389
Summary389
Chapter 11Infrast


Login

  |  

Complaints

  |  

Blog

  |  

Games

  |  

Digital Media

  |  

Souls

  |  

Obituary

  |  

Contact Us

  |  

FAQ

CAN'T FIND WHAT YOU'RE LOOKING FOR? CLICK HERE!!!

X
WonderClub Home

This item is in your Wish List

Expert One-on-One J2EE Design and Development, What is this book about?
The results of using J2EE in practice are often disappointing: applications are often slow, unduly complex, and take too long to develop. Rod Johnson believes that the problem lies not in J2EE itself, but in that it is often, Expert One-on-One J2EE Design and Development

X
WonderClub Home

This item is in your Collection

Expert One-on-One J2EE Design and Development, What is this book about?
The results of using J2EE in practice are often disappointing: applications are often slow, unduly complex, and take too long to develop. Rod Johnson believes that the problem lies not in J2EE itself, but in that it is often, Expert One-on-One J2EE Design and Development

Expert One-on-One J2EE Design and Development

X
WonderClub Home

This Item is in Your Inventory

Expert One-on-One J2EE Design and Development, What is this book about?
The results of using J2EE in practice are often disappointing: applications are often slow, unduly complex, and take too long to develop. Rod Johnson believes that the problem lies not in J2EE itself, but in that it is often, Expert One-on-One J2EE Design and Development

Expert One-on-One J2EE Design and Development

WonderClub Home

You must be logged in to review the products

E-mail address:

Password: