ExpertOne-on-One J2EE Development Without EJB：英文原版

5星 · 超过95%的资源需积分: 9 56 浏览量更新于2024-07-25 收藏 8.14MB PDF 举报

"ExpertOne-on-One™ J2EE™ Development without EJB™ 是一本由 Rod Johnson 和 Juergen Hoeller 合著的专业书籍，探讨了在 J2EE 开发环境中不依赖 Enterprise JavaBeans (EJB) 的方法。这本书由 Wiley Publishing, Inc. 在2004年出版，并同时在加拿大发行。内容涵盖了对 J2EE 平台中替代 EJB 的技术和策略，旨在提供一种更灵活、更轻量级的开发实践。" 本书针对的是那些希望在 J2EE 开发中避免使用 EJB 的开发者，因为 EJB 通常被认为是复杂且重量级的解决方案。作者 Rod Johnson 和 Juergen Hoeller 提供了他们的专业见解和实战经验，指导读者如何利用其他技术来实现相同的功能，比如使用 Spring 框架，该框架是 Rod Johnson 创建的，已经成为 Java 企业应用开发中的重要组成部分。书中强调了在不使用 EJB 的情况下，如何实现服务层、持久化层和事务管理等关键功能。通过这种方式，开发者可以构建出更易于维护、扩展和部署的应用程序。此外，书中可能还讨论了如何通过简化架构来提高开发效率，减少系统的复杂性，以及如何适应不断变化的需求。虽然 EJB 在某些场景下提供了强大的企业级服务，但其学习曲线陡峭，配置和管理成本较高。这本书的出现，是为了给开发者提供一种新的思考方式，即在不牺牲可靠性或可扩展性的情况下，使用更轻量级的技术栈。书中可能包含具体的代码示例、最佳实践和案例研究，以帮助读者理解和应用这些理念。值得注意的是，出版商和作者对于本书内容的准确性和完整性不做任何明示或默示的保证，他们不承担因使用本书内容而产生的任何损害责任。如果需要专业帮助，应当寻求合格专业人士的服务。书中引用的组织或网站仅供参考，不应被视为对信息来源的保证。 "J2EE Development without EJB" 是一本关于如何在 J2EE 环境中使用非 EJB 技术进行高效开发的重要参考资料，特别适合那些寻求简化开发流程、提升开发效率的 Java 专业人员。

Chapter Title

Coverage Analysis and Other Test Tools 443

Test Generators 444

Coverage Tools 444

Mutation Testing Tools 447

Resources 448

Summary 449

Chapter 15: Performance and Scalability 451

Definitions 452

Setting Clear Goals 453

Architectural Choices: The Key to Performance and Scalability 454

Object Distribution, Clusters, and Farms 455

Data Access 461

Other Architectural Issues 462

Implementation Choices 463

The Performance Implications of Dispensing with EJB Service Provision 463

Caching and Code Optimization 471

Tuning and Deployment 476

JVM 476

Application Server 476

Framework Configuration 477

Database Configuration 477

An Evidence-based Approach to Performance 478

Benchmarking 479

Profiling 480

Diagnostics 484

Resources 485

Summary 485

Chapter 16: The Sample Application 489

Pet Store Requirements 490

The iBATIS JPetStore 3.1 490

Middle Tier 491

Remoting 493

Room for Improvement 494

Spring JPetStore 494

Middle Tier 496

Data Access Tier 499

Web Tier 502

Remoting 510

02_558315 ftoc.qxd 5/28/04 12:31 PM Page xv

Introduction

This is a fairly short book, given its scope, because its subject is less complex than you’ve been led to

believe.

J2EE orthodoxy makes heavy work of many simple problems. Indeed it sometimes seems that the J2EE

industry is committed to the belief that there are no simple problems.

Many—probably most—J2EE applications are over-engineered, with unnecessarily complex architec-

tures. Over-engineering can be very costly. J2EE developers tend to assume that increased cost up front

will be more than balanced by reductions in future costs. Unfortunately, karma doesn’t apply to software

engineering, and this is often a fallacy. Greater complexity up front means more code to write and main-

tain, more potential for bugs, more delay in demonstrating functionality to users: ultimately, greater

chance of failure, and at greater cost.

J2EE over-engineering usually involves EJB. As I pointed out in Expert One-on-One J2EE Design and

Development, EJB is often used inappropriately. This is a real problem, because EJB can introduce more

complexity than it conceals. Some services provided by EJB are also overrated. For example, few experi-

enced developers or architects who have worked with entity EJBs to access relational data want to repeat

the experience—at least, given the alternatives of JDO, Hibernate, and other transparent persistence

technologies.

Critiques of EJB have become commonplace since late 2002. It’s easy enough to pick the flaws in an

imperfect existing technology, without suggesting alternatives. This book breaks new ground in describ-

ing and illustrating better approaches for the majority of J2EE applications that derive no benefit from

EJB. This book is no mere theoretical discussion, but a practical guide to designing and implementing

high-performance J2EE applications on time and budget. Our suggested architectures are backed up by

extensive experience, a realistic sample application, and comprehensive open source solutions that meet

typical infrastructure needs.

Despite the significant problems that have emerged with EJB, it continues to be adopted too often largely

because of fashion and fear. Fashion because even nontechnical managers have heard of EJB and because

many books on J2EE architecture barely mention alternatives to EJB for delivering enterprise services,

even where excellent alternatives exist. Fear that the alternatives are worse: for example, that without

EJB developers will be left to handle complex issues such as transaction management without the train-

ing wheels of the EJB container. This book aims to show that these fears are largely unfounded. Where

the potential complexity is real, it shows that there are alternatives that do a better job than EJB at

addressing the problems concerned.

This book demonstrates a much simpler approach to developing typical J2EE appli-

cations than the “classic” J2EE blueprints approach exemplified by the original Java

Pet Store. Our approach leads to reduced cost, shorter time to market, greater main-

tainability, and better performance.

03_558315 flast.qxd 5/28/04 12:31 PM Page xvii

xviii

Introduction

The architectural approach described in this book is part of a growing movement towards simpler, more

rational J2EE architectures. It’s suitable for use with agile methodologies. It draws on recently developed

technologies such as Aspect Oriented Programming, and borrows where appropriate from alternative

platforms to J2EE such as .NET.

I aim to help you build the simplest possible applications that meet your requirements—and hence, also

the cheapest, most maintainable and testable.

The merits of EJB have become a surprisingly emotive issue in the J2EE community. There seems to be a

stark polarization between those would never use EJB unless compelled and those who believe that the

EJB skeptics are lazy, ignorant heretics, with little middle ground.

As you may suspect, I’m not a fan of EJB. However, I have developed many applications with EJB and

speak from experience and intimate knowledge of the EJB specification. I’ll also strive to justify my position

throughout this book. My goal is to help you develop effective applications, not to combat the use of EJB.

After reading this book, you should be able to assess the value proposition of EJB for each application. If,

with a strong understanding of EJB and the alternatives, you believe that your requirements are best

addressed by EJB, use EJB. The message of this book is not a black-and-white “don’t use EJB.”

Who This Book Is For

This book is for J2EE architects and developers who have a solid grasp of the technology and want to

use it more productively. It’s a book about the why and how of enterprise applications, rather than the

what. So you won’t find API listings here, and you won’t find yet another introduction to basic J2EE ser-

vices such as JNDI and JTA. There are many good books and articles that address these topics.

The material in this book is particularly relevant to those working on web applications. However, most

J2EE developers will find something of value. You may well read this book and decide that EJB is the

correct choice for your particular application; even in this case, by applying the criteria set out in this

book, you’ll know exactly why you are using EJB and what value it is providing.

Aims of This Book

This book aims to help you solve practical problems. It aims to demonstrate a simpler and more produc-

tive approach to J2EE development than the traditional J2EE approach exemplified in Sun blueprints

and based on the use of EJB to manage business logic.

You might end up having a lot more fun, as well.

What This Book Covers

This book covers:

❑

Problems with EJB and received wisdom in J2EE architecture

❑

Key values for successful J2EE projects

03_558315 flast.qxd 5/28/04 12:31 PM Page xviii

xix

Introduction

❑ Effective architectures for J2EE applications, especially for web applications

❑

Common mistakes in J2EE architecture and implementation

❑

How to find the simplest and most maintainable architecture for your application

❑

Inversion of Control and Aspect-Oriented Programming: two important new technologies that have

recently become important to J2EE development.

Chapters 6 through 12 cover replacing EJB services with lighter-weight, more testable alternatives. We

emphasize:

❑

Transaction management. This is an essential of enterprise applications, and a popular motivation for

using EJB. We’ll look at alternative means of transaction management, discussing both declarative

and programmatic transaction management.

❑

Data access in J2EE applications: another central problem that—in contrast to transaction manage-

ment—EJB addresses very badly.

❑

How AOP can be used to solve many common problems in enterprise software development.

We’ll also talk about:

❑

Web tier design, and the place of the web tier in a well-designed J2EE application

❑

Testing and test-driven development, and how to test J2EE applications effectively

❑

Performance and scalability

Specific technologies considered include:

❑

Data access with JDBC, Hibernate, and JDO

❑

Web tier technologies such as Struts, WebWork, Spring MVC, and JSP

❑

Using open source products to develop a strong application infrastructure, and minimize the amount

of code you’ll have to develop, test, and maintain in house. Most problems of J2EE infrastructure

have been solved by leading open source products; I’ll help you focus on tackling those unique to

your applications.

Assumed Knowledge

This is not a primer on EJB or J2EE.

We assume knowledge of core J2EE APIs and services such as JNDI, JTA, and database connection

pooling.

We assume sound knowledge of J2SE, including reflection, inner classes, dynamic proxies, JDBC, JAXP,

and JNDI.

We assume good working knowledge of OO design.

03_558315 flast.qxd 5/28/04 12:31 PM Page xix

剩余577页未读，继续阅读

congcongrong11

粉丝: 0
资源: 2

ExpertOne-on-One J2EE Development Without EJB：英文原版

Expert One-on-One J2EE Development Without EJB

专家一对一J2EE开发不使用EJB

J2EE开发：不使用EJB的实战指南

中文版EXPERT.ONE.ON.ONE.J2EE.DEVELOPMENT.WITHOUT.EJB.10

中文版EXPERT.ONE.ON.ONE.J2EE.DEVELOPMENT.WITHOUT.EJB.08

中文版EXPERT.ONE.ON.ONE.J2EE.DEVELOPMENT.WITHOUT.EJB.09

中文版EXPERT.ONE.ON.ONE.J2EE.DEVELOPMENT.WITHOUT.EJB.part2

中文版EXPERT.ONE.ON.ONE.J2EE.DEVELOPMENT.WITHOUT.EJB.pdf1

中文版EXPERT.ONE.ON.ONE.J2EE.DEVELOPMENT.WITHOUT.EJB.part3

中文版EXPERT.ONE.ON.ONE.J2EE.DEVELOPMENT.WITHOUT.EJB.pdf3

最新资源