ejb3

First we need an EJB3 application to start with .

首先，我们需要从一个EJB3应用开始。

You can also use it in complete isolation from EJB3 .

还可以完全独立于EJB3使用Seam。

Design your database model by writing Ejb3 entity beans .

通过写Ejb3实体Bean设计数据库模型。

So , in most examples throughout this book , we use EJB3 components .

所以，本书的大多数例子我们都使用EJB3组件。

Well , Grails doesn 't require that you have an EJB3 application as your starting point .

Grails并不需要你以一个EJB3应用作为起点。

EJB3 makes XML files completely optional , and it is definitely a step toward the right direction .

EJB3完全可选择的使用XML文档，它向正确方向迈出了积极的一步。

So , why would anyone want to use POJO components when deploying in an EJB3 container ?

所以当在EJB3容器中进行部署时，为什么每个人都想使用POJO组件？

Because I am using EJB3 for my implementation examples , I 'll show you the implementation using programmatic transactions .

由于我在实现示例中使用的是EJB3，因此我将展示使用程序化事务的实现。

The manager component is an EJB3 session bean and we will discuss it in the next section .

名为manager的组件是一个EJB3的会话bean，我们将在下节讨论该话题。

EJB3 is a major update to the EJB specification that greatly simplifies EJB programming .

EJB3是对EJB规范的重大更新，此更新极大地简化了EJB编程。

However , POJOs also have less features than EJB3 components since POJOs cannot get EJB3 container services .

但是，POJO比EJB3的功能少，因为POJO不能获得EJB3容器服务。

But all in all , their application is much smaller than EJB3 components , especially in small to middle sized applications .

但是总的来说，它们的应用要比EJB3组件少，特别是在中小型应用中。

In a Seam application , it adds the Seam interceptor to all EJB3 classes .

在一个Seam应用中，它能将所有的EJB3类加入Seam拦截器。

Seam adds to EJB3 annotations and expands the annotation-based programming model to the entire web application .

Seam加入了EJB3的注解，为整个web应用拓展了基于注解的编程模型。

Because EJB3 is not required , the target of the deployment can be any basic servlet container .

因为不需要EJB3，所以部署的目标可以是任何基本的servlet容器。

We specify the deployment metadata of the EJB3 session bean using annotations in the bean class .

我们通过在Bean类中使用注释来指定EJB3会话Bean的部署描述符。

EJB3 is the effort by the official Java standardization body to promote the use of annotations in enterprise Java components .

EJB3是Java官方标准化机构促进Java企业组件中注解使用的一项成果。

So , let 's see what it takes to build a Grails application backed by EJB3 entity beans .

那么，让我们看看基于EJB3实体Bean构建Grails应用要做哪些工作。

You can actually leverage much of Seam 's power without even a reference to an EJB3 jar or descriptor file .

实际上，即使完全不引用EJB3jar或描述符文件，也可以使用Seam的很多功能。

It extends the EJB3 annotated POJO ( plain old Java objects ) programming model to the entire web application .

它为整个web应用拓展了基于注解的EJB3POJO编程模型。

JPA was created as part of the EJB3 specification and is an inherent part of EJB3 .

JPA作为EJB3规范的一部分被创建，而且是EJB3的固有部分。

So far we have seen the Web application invoking EJB2.1 and EJB3 session beans with unrestricted method access .

到目前为止，我们看到的都是Web应用程序使用无限制的方法访问调用EJB2.1和EJB3会话Bean。

However , the general assumption of this article is that you 're interested in incorporating RAD web development into your EJB3 project .

但是，本文的一般性假设是你有兴趣将RADWeb开发并入你的EJB3项目。

The Java Persistence API ( JPA ) represents a major enhancement to persistence programming of the EJB3 specification .

JavaPersistenceAPI（JPA）代表了对EJB3规范持久性编程的重大增强。

The bounded set of annotations that do depend on an EJB3 container are geared specifically for that environment .

的确依赖于EJB3容器的一组有限的注释则是专用于那个环境的。

However , when you do have an EJB3 environment , you can use this approach to separate your Spring and JPA configurations .

但是，当您拥有EJB3环境时，可以使用此方法分离Spring和JPA配置。

However , realizing the coming support for EJB3 , we moved all of the facade logic into a POJO .

然而，考虑到对将来EJB3的支持，我们将所有的Facade逻辑转移到一个POJO中。

Most Java EE5.0 web applications will have both EJB3 modules for business logic and JSF modules for the web front end .

大多数的Web应用都将包含有业务逻辑的EJB3组件和Web应用前端显示的JSF组件。

For instance , we can make ManagerAction a POJO instead of a EJB3 session bean .

例如，我们能将ManagerAction转化为一个POJO，而不是一个EJB3sessionbean。

We suddenly have all the enterprise-level capabilities of JEE / EJB3 and the benefits of RAD web application development !

我们瞬间就拥有了JEE/EJB3的企业级能力和RADWeb应用开发的全部好处！