Listing 3. Person POJO, take 3.

清单3。

Listing 2. Person POJO, take 2.

清单2。

Next, you will create your Session Bean pojo.

接下来将创建会话Bean pojo。

Create the POJO with the appropriate annotations.

创建具有适当注解的POJO。

POJO programming seeks to simplify this task.

但 POJO 编程可以简化这一任务。

Invoking rule service using the POJO session.

使用POJO会话调用规则服务。

The result is a simple POJO, as shown in Figure 29.

得到的结果是一个简单的POJO，如图29所示。

I only need to create a simple POJO and annotate it.

我只需要创建一个简单的POJO并对它进行注释。

Fined-grained POJO and coarse-grained database tables.

细粒度的POJO和粗粒度的数据表。

We have chosen to consume a POJO to keep things simple.

出于简单考虑，本用例中我们选择消费一个POJO。

You also can mark a read-only POJO immutable as a tuning hint.

将只读POJO标识为不可更改的(immutable)也是一个调优点。

There are two ways to build a composite POJO at your service layer.

有两种方式在服务层构建组合POJO。

The code in Listing 9 illustrates the simple HelloWorld POJO class.

清单9中的代码说明了简单的HelloWorld pojo类。

As a result, your backing bean, CourseAction, becomes a simple POJO.

因此，支持bean (CourseAction)成为简单的POJO。

POJO-based programming — Lightweight containers are not invasive.

基于POJO的编程——轻量级容器不具侵犯性。

It is not intended to describe all the scenarios around SCA POJO usage.

但本文并不打算描述所有与SCA POJO使用有关的场景。

Do this by creating a POJO that implements the "serializable" interface.

操作方法是创建一个实现这个“可序列化”接口的POJO。

So, Listing 1 is a POJO that represents information about fishing lures.

所以，清单1是一个表示鱼饵信息的POJO。

Any POJO that implements the resource is known as the resource class.

实现资源的POJO被称为资源类。

This method is generated for each reference defined by a POJO component.

将为POJO组件定义的每个引用生成此方法。

Now that the POJO is complete, it's time to write the serialization code.

既然POJO已经创建完成了，下面就该编写序列化代码了。

Figure 14 shows the model of the rule set invocation using SCA POJO component.

图14显示使用SCA POJO组件调用规则集的模型。

Write your business logic with session beans, Spring, Guice, or Pojo services.

用会话Bean、Spring、Guice或Pojo服务写业务逻辑。

You could also add new properties to the POJO without affecting the client.

你还可以在不影响客户端的前提下为POJO添加新特性。

POJO delegate classes are often used simplify invoking services in a common way.

通常，以通用的方式使用POJO委托类来简化对服务的调用。

It is implemented as a POJO with methods to get and set the attribute values.

它作为一个POJO实现，带有获取和设置属性值的方法。

Finally, you can have named native queries, and map the results back to a POJO.

最后，您可以拥有命名本机查询，并将结果映射回POJO。

The programming model also defines a detachment model for the POJO (Entity) objects.

该编程模型还定义了 POJO（实体）对象的分离模型。

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

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

There is one SCA POJO component, which is the bridging/mapping code discussed earlier.

还有一个 SCA POJO 组件，它是前面讨论的桥接/映射代码。