Use interception and AOP to attach services to POJOs
使用拦截和AOP，将服务与 POJO 相关联
Very often your front-end UI needs data from several different POJOs.
你的前端ui经常需要来自多个不同POJO的数据。
You'll also have to provide any mapping files required for your POJOs.
您还需提供POJO所需的所有映射文件。
There is no support for declarative method-level transaction in POJOs.
POJOs中将不在支持方法级别事务声明（declarative method-level transaction）。
For example, you get to use a simpler programming model based on POJOs.
例如，您可以使用一个更加简单、基于POJO的编程模型。
Build a container that accepts POJOs, rather than restricted components.
构建一个接受POJO的容器，而不是受限制的组件。
Spring lets you configure only the services you need and apply them to POJOs.
Spring让您可以只配置您需要的服务并将它们应用于POJO。
All of this means that you can immediately begin using POGOs as a replacement for your POJOs.
所有这些意味着您可以立即开始使用POGO作为POJO的替代选择。
The question, of course, is how do those POJOs interact with each other to form an application?
当然，问题是如何使POJO交互来组成这个应用？
The second is pojoA has one-to-many associations with many other POJOs such as pojoB and pojoC.
第二种场景，pojoA和很多其他POJO有one-to-many关联，例如pojoB和pojoC。
I agree that coding POJOs without tools makes EJB development difficult. In the EJB 3.0 specification.
我承认，不使用工具对POJO进行编码使得开发很困难。
Seam allows developers to use the "same kind of stuff", annotated POJOs, for all application components.
Seam允许开发者将“同一种东西”——有注解的POJOs——应用与所有的应用组件。
As a result, developers can focus on the business logic, and unit test their POJOs without the framework.
因此，开发者可以利用POJO开发业务逻辑和进行单元测试而不必考虑框架。
The session facade provides adapter logic to map Hibernate entity POJOs to Service Data Objects and back.
会话Facade提供适配器逻辑，以便将Hibernate实体POJO映射到服务数据对象，以及进行反向映射。
It is straightforward, easy to use, and POJOs are much easier to comprehend than the notion of an "entity."
它很简单且易使用，而且POJO比“实体”概念更易于理解。
The Order Processor interacts with the JPA entity manager and the JPA POJOs to accomplish its persistence code.
OrderProcessor与JPA实体管理器和 JPAPOJO 交互以完成其持久性代码。
Your POJOs contain only your business logic, and the framework adds what you need to build enterprise applications.
POJO仅包含业务逻辑，而 Spring框架添加了构建企业应用程序所需的内容。
The interface extension feature of XMLBeans allows you to add methods with custom implementation for the generated POJOs.
XMLBeans的接口扩展特性允许在生成的POJO中添加具有定制实现的方法。
Simple also facilitates the reverse: Developers can translate XML documents into pojos-a process known as deserialization.
Simple也可促进相反的过程：开发人员可以将XML文档转换成POJO—即所谓的反序列化(deserialization)过程。
A compromise is to generate a "business delegate" and associated session EJB components from the Task POJOs as shown in Figure 5.
折衷的方法是生成“业务代表”并与TaskPOJO中的会话ej b组件相关联，如图5所示。
The model is designed to enable application building using POJOs so that they can be used inside and outside of an OSGi application.
模型设计的目的是使用POJO支持应用程序构建，以便于它们在OSGi应用程序内部和外部使用。
Remoting: by adding annotations on POJOs or by using Spring XML configuration, integrate with remote invocations and async remoting.
远程化：通过添加POJO的注解或者使用SpringXML配置来与远程调用和异步远程化集成。
XMLBeans is a data-binding framework that creates POJOs from an XML Schema, allowing you to read, manipulate, and write XML quickly.
XMLBeans 这种数据绑定框架可以从XML模式创建POJO，允许快速地读取、操作和写 XML。
The Geronimo platform provides frameworks and tools that you can use to build a flexible, scalable, and maintainable SOA using POJOs.
Geronimo平台提供了框架和工具，您可以使用它通过 POJO构建灵活的、可扩展的和可维护的SOA。
At the same time, Seam expands the EJB3 component model to POJOs and brings the stateful context from the web tier to the business components.
同时，Seam拓展了EJB3到POJO的组件模式，从we b层到业务层都有了状态上下文。
The data layer consists of defined XML files that will be consumed by the Spring framework and returned as POJOs to the simulator service layer.
数据层包含已定义的XML文件，Spring框架会使用这些文件并作为POJO返回到模拟器服务层。
The framework "wires" application services to the POJOs by intercepting the execution context or injecting service objects to the POJO at runtime.
框架通过两种方式将应用服务与运行中的POJO关联起来：拦截POJO的执行上下文或将服务对象注入POJO中。
If all your business components are Seam POJOs, you can run your Seam application outside of the EJB3 application server (see Chapter 23, Seam Without EJB3).
如果你的所有业务组件都是SeamPOJO，那么你就能不依赖EJB3应用服务器，运行你的Seam应用(参见23章，没有EJB3的Seam)。
AOP lets you attach these aspects to POJOs, then specify a point in time (like the beginning of a method or exception generation) and another aspect to attach.
AOP使您可以将这些方面联系到POJO，然后指定一个时间点(如方法开始时或产生异常时)和另一个需要联系的方面。
Yet the service implementation might use a data binding tool to convert the XML document carried in the payload of the SOAP message into objects, such as POJOs.
服务实现还可能使用数据绑定工具将SOAP消息负荷中的XML文档转化成对象，如POJO。
应用推荐