POJO programming seeks to simplify this task.
但 POJO编程可以简化这一任务。
Invoking rule service using the POJO session.
使用POJO会话调用规则服务。
Input: POJO-annotated beans (and optional templates).
输入：带注解的POJObean(和可选的模板)。
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中的代码说明了简单的HelloWorldpojo类。
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.
但本文并不打算描述所有与SCAPOJO使用有关的场景。
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组件定义的每个引用生成此方法。
Figure 14 shows the model of the rule set invocation using SCA POJO component.
图14显示使用SCAPOJO组件调用规则集的模型。
Write your business logic with session beans, Spring, Guice, or Pojo services.
用会话Bean、Spring、Guice或Pojo服务写业务逻辑。
Figure 5 is the class diagram for the session bean and the corresponding POJO.
图5是该会话Bean和对应的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。
Deploying a POJO in Axis2 is merely three lines of code, as shown in Listing 2.
在Axis2中部署POJO仅需要三行代码，如清单2中所示。
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.
还有一个SCAPOJO组件，它是前面讨论的桥接/映射代码。
Next, you instantiate the POJO by invoking the read method from the Serializer object.
接下来，通过从Serializer对象调用read方法，从而实例化POJO。
The final runtime artifact contained within our scenario is also implemented as a POJO.
我们的场景中包含的最后一个运行时工件同样被实现为一个POJO。
First, the COBOL client is not affected by changing the POJO location or package name.
首先，改变POJO位置或软件包的名字不会影响COBOL客户端。
All that having been said, the domain objects still retain a lot of their POJO nature.
虽然有上述各种情况，域对象依然保留许多pojo特性。
The configuration scheme is represented by another POJO that is described in Listing 7.
配置方案由另一个POJO表示，描述在清单7中。
These scenarios give meaningful use cases that demonstrate the need for POJO components.
这些场景就是相当有意义的用例，说明了对 POJO 的需求。
应用推荐