从新手到专业：EJB3应用开发指南

需积分: 0 100 浏览量更新于2024-07-28 收藏 6.97MB PDF 举报

"BEGINNING EJB 3 APPLICATION DEVELOPMENT" 《 Beginning EJB 3 Application Development》是一本专为Java EE 5 API，特别是EJB 3技术提供深入指导的书籍。这本书由Raghu R. Kodali, Jonathan Wetherbee与Peter Zadrozny共同编写，并由Floyd Marinescu（《EJB Design Patterns》的作者）作序。它旨在帮助初学者到专业人士全面掌握基于EJB 3的应用程序开发。 EJB（Enterprise JavaBeans）是Java平台上的企业级组件模型，用于构建可部署在服务器端的分布式应用程序。EJB 3是其一个重要的版本，引入了许多简化开发的特性，如注解驱动的编程模型，使得EJB更轻量级、易于使用。本书涵盖了以下核心知识点： 1. **EJB 3基础**：介绍EJB 3的基本概念，包括实体Bean（Entity Beans）、会话Bean（Session Beans）和消息驱动Bean（Message-Driven Beans），以及它们在Java EE 5架构中的角色。 2. **注解驱动开发**：EJB 3引入了注解，允许开发者在类和方法上直接标注元数据，减少了XML配置的需求。书中会讲解如何使用@Stateless、@Stateful、@Singleton、@PersistenceContext和@PersistenceUnit等注解。 3. **容器管理的持久性（CMP）**：EJB 3中的实体Bean可以通过容器管理的持久性来处理数据库交互，降低了对JDBC和SQL的依赖。 4. **Java Persistence API (JPA)**：JPA是EJB 3的一部分，提供了对象/关系映射（ORM）功能，用于管理数据库中的对象。书中会详细介绍JPA的使用，包括实体关系映射、查询语言（JPQL）和 Criteria API。 5. **事务管理**：EJB 3支持声明式事务管理，开发者可以不用显式地控制事务边界，而是通过注解来定义事务属性。 6. **安全性**：EJB 3提供了内置的安全机制，包括角色基的安全性和方法级别的访问控制。书中会讲解如何配置和使用这些安全特性。 7. **会话Bean的生命周期和并发管理**：探讨了无状态和有状态会话Bean的生命周期，以及如何处理并发访问。 8. **分布式计算**：EJB 3允许创建可跨多个节点的分布式应用程序，书中会讲解如何设计和实现这样的解决方案。 9. **集成与测试**：介绍如何与其他Java EE组件（如Servlets、JSP、JSF）集成，以及如何进行单元测试和集成测试。 10. **最佳实践与案例研究**：书中包含实际项目案例，提供从零开始构建EJB 3应用的详细步骤，帮助读者理解并掌握最佳实践。通过阅读此书，读者将能够熟练地利用EJB 3技术构建高效、可靠的Java EE应用程序和服务，从而从新手成长为专业开发者。

■CHAPTER 10 Migrating EJB 2.x Applications to EJB 3 . . . . . . . . . . . . . . . . . 321

Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322

Session Bean Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

EJB 2.1 Session Bean. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

EJB 2.1 ejb-jar.xml File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

EJB 3 Session Bean Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

Migrating the EJB 2.1 Session Bean Class . . . . . . . . . . . . . . . . . . . . 326

Migrating the EJB 2.1 Session Bean Interfaces . . . . . . . . . . . . . . . . 327

Migrating the EJB 2.1 Session Bean ejb-jar.xml Properties. . . . . . 328

Migrating an EJB 2.1 Web Service Endpoint Interface . . . . . . . . . . 330

Session Bean Migration Wrap-Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

MDB Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

Entity Bean Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

EJB Client Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

Migrating an EJB 2.1 Session Bean Client . . . . . . . . . . . . . . . . . . . . 335

End-to-End EJB Application Migration Example . . . . . . . . . . . . . . . . . . . . 336

EJB 2.1 Application Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

EJB 3 Application Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348

Migrating Our Application to Run Outside a Java EE Container. . . . . . . . 355

EJB 3 Session Bean Class Running Outside the EJB Container . . 356

EJB 3 persistence.xml File with an Outside-the-Container

Persistence Unit

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

EJB 3 Application-Managed EntityManager Client. . . . . . . . . . . . . . 358

Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359

■CHAPTER 11 EJB 3 Deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

A Note on Deployment Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362

Overview of the Deployment Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

The Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

The Assembler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

The Deployer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

Java EE Deployment Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

The Java EE Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

The Java EE Containers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

■CONTENTS xv

6714FMcmp3.qxd 8/31/06 7:06 PM Page xv

■CONTENTSxvi

Java EE Deployment Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

The Java EE Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

Java EE Module Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

Library Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372

Application Servers and Platform Independence. . . . . . . . . . . . . . . . . . . . 375

Deployment Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376

The Deployment Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376

Deployment Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376

The Application Assembler. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377

The Application Deployer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380

Assembling an EJB JAR Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381

Naming Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382

Assembling a Persistence Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382

Naming Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383

Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383

■CHAPTER 12 EJB 3 Client Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385

Application Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385

JSF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390

Evolution of Java EE Web Technologies . . . . . . . . . . . . . . . . . . . . . . . 391

JSF Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393

JSF Tools and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395

Developing Web Applications Using JSF and EJB . . . . . . . . . . . . . . . . . . . 396

The Login Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398

The New Customer Registration Page . . . . . . . . . . . . . . . . . . . . . . . . 402

The Links Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409

The Search Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413

The Wine List Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419

The Display Selected Wine Details Page . . . . . . . . . . . . . . . . . . . . . . 423

The Display Cart Items Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428

The Notification Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431

Packaging, Deploying, and Testing the Application . . . . . . . . . . . . . . . . . . 432

Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432

Compiling and Packaging the JSF Application . . . . . . . . . . . . . . . . . 433

6714FMcmp3.qxd 8/31/06 7:06 PM Page xvi

EJB 3 is a very important milestone for the specification. Not only is it significantly eas-

ier to use, but also for the first time (in my opinion), the specification is now built around

the proven needs of the development community, standardizing existing best practices

instead of being the result of design by committee. The reader of this book is most likely a

developer, so I will present some historical context of how EJB came to be and why it

matters today, from the perspective of developers.

I speak at conferences fairly often, and at a certain point during a talk I will ask the

audience how many have used EJB. Usually, 90 percent put up their hand. Then, I ask

them, “How many of you have used EJB as distributed objects—meaning, where you have

a separate physical tier for your business logic and a separate tier for your presentation

(servlets/JSP) tier?” Usually only 15 percent of the 90 percent will put up their hand.

These results have been consistent at conferences I’ve spoken at in North America,

Europe, and Japan. The result still never ceases to amaze me, since the early days of EJB

forced you to apply distributed semantics on your code, which is useful on large-scale

multi–physical tier projects—but in fact, most of the EJB audience was using it as a local

framework for their small-to-medium-sized web apps.

Why is this so? If you look at the wider context of the times (1999 to 2003), it starts to

make sense. If you look at the core values that EJB 1+ proposed, you could boil them all

down to three simple categories:

• Framework benefits: At the time, if you were doing any kind of web or enterprise

development in Java, you were living in a proprietary, confusing world; or you were

using nuts-and-bolts tools like RMI and servlets, and creating your own frame-

works. Couple that with the fact that during this time, most software developers

were new, attracted by the dot-com boom—the industry was just waiting to be

given a standard, agreed-upon way to do enterprise development. EJB provided

that—a standard framework for handling transactions, security, stateful compo-

nents, object persistence, and so on. Having a standard framework solved a real

and present need—since at the time there was no open source movement and

there were no web frameworks.

• Distribution benefits: EJB standardized a programming model and platform for

building business logic with distributed objects. Hot on the heels of RMI and

CORBA, this too was needed. If you wanted to do distributed objects, EJB was the

answer.

xix

Foreword

6714FMcmp3.qxd 8/31/06 7:06 PM Page xix

剩余509页未读，继续阅读

haha875232

粉丝: 4
资源: 92

从新手到专业：EJB3应用开发指南

精通EJB3应用程序开发：从新手到专业

EJB3应用开发入门：从新手到专业

从新手到专家：EJB3应用开发指南

EJB3的三本好书第1本 Beginning EJB3 Application Development From Novice to Professional

Beginning_EJB_3_Application_Development_From_Novice_to_Professional-3100.zip

EJB3的三本好书第3本 Mastering EJB3 4ed

ejb3 带源码

EJB3的三本好书第2本, EJB3 in Action 2007

入门指南：EJB3应用开发实战与Glassfish详解

基于springboot共享经济背景下校园闲置物品交易平台源码数据库文档.zip

最新资源