Check Use the data source in container managed persistence (CMP).
选取usethedatasourceincontainermanaged persistence (CMP)。
Check the option to enable the data source for container-managed persistence.
选中该选项为容器管理持久性启用数据源。
While not enforced, optimistic locking is highly recommended in flow-managed persistence.
尽管不是强制实施的，但是强烈建议在流管理的持久化中使用乐观锁。
That is a noticeable difference between Spring Web flow's flow-managed persistence and a Seam conversation.
这是SpringWebFlow的流管理的持久化和Seam对话之间的一个显著区别。
With container-managed persistence, when an entity bean is created, its information is saved in the database.
在创建一个实体bean时，容器管理的持久性会将其信息保存在数据库中。
The container managed persistence being based on the EJB model is again overly complex to develop and manage.
基于EJB模型的容器持久化管理的开发和管理过于复杂。
This approach to flow-managed persistence matches exactly how JPA 1.0 interprets the handling of a conversation.
流管理持久化使用的这种方法与JPA 1.0解释对话处理的方式是完全一致的。
The access intent policies discussed in this article apply to Container Managed Persistence (CMP) 2.x beans only.
在本文中讨论的访问意图策略只能在容器管理持久性(CMP) 2 .xbean上应用。
For each container-managed EM instance, there are one or more corresponding container-managed persistence contexts (PC).
对于每个容器管理的em实例，都存在一个或多个对应的容器管理的持久性上下文(Persistence Contexts,PC)。
This is a great advantage of using read-only transactions over non-transactional data access in flow-managed persistence.
这是在流管理持久化中使用只读事务优于使用非事务性数据访问的地方。
Container-managed persistence (CMP) entity beans handle all of the persistence semantics automatically, in the container.
容器管理的持久性(CMP)实体bean在容器中自动处理所有持久性语义。
Bean-managed persistence leaves all the work to the EJB developer to figure out how to store and retrieve a specific object type.
Bean管理的持久性将所有的工作交给EJB开发人员，让他们确定如何存储和检索特定的对象类型。
The persistence bundle makes use of another standard feature of enterprise OSGi, JPA integration, to take advantage of managed persistence.
持久性bundle使用企业osgi的另一个标准特性—JPA集成—来利用托管持久性。
Since the usage of OpenJPA in this article is for an application-managed persistence environment, you can use any of these OpenJPA releases.
由于本文所介绍的OpenJPA使用针对一个应用程序管理的持久化环境，您可以使用下列任何OpenJPA版本。
With container Managed persistence (CMP) entity beans, the container generates the persistence code as well as managing the persistence logic.
使用容器管理的持久性(Container Managed Persistence,CMP)实体bean时，容器生成持久性代码并管理持久性逻辑。
Flow-managed persistence is intended to address Spring Web Flow use cases that are considered atomic from the perspective of transactions.
流管理持久化旨在处理那些从事务角度来说属于原子性的SpringWebFlow用例。
This has interesting implications for the question of whether to use no transactions or read-only transactions in flow-managed persistence.
这对于在流管理的持久化中是不使用事务还是使用只读事务的问题产生了有趣的影响。
With Bean Managed Persistence (BMP) entity beans, the developer writes the persistence code but the container determines when to execute that code.
使用bean管理的持久性（Bean Managed Persistence，BMP）实体 bean 时，开发人员编写持久性代码而容器确定何时执行该代码。
Code your application using the JDBC DataSource interface for connections (or use container-managed persistence (i.e. EJBs), but that is another topic).
使用用于连接的JDBCDataSource接口编写应用程序(或者使用容器管理的持久性，但那是另一个话题)。
The first one, which USES Container-Managed Persistence (CMP) to provide object-based access to a simple database table, is called PhoneBookEntryBean.
第一个类使用容器管理持久性(Container - Managed Persistence,CMP)来提供对简单数据库表phonebookentrybean的基于对象的访问。
"Right now I am working on finishing JPA support with container-managed persistence," he told me when I sat down to talk to him just before Thanksgiving.
“我现在的工作是，借助容器管理的持久性来完成JPA支持”，感恩节前夕我坐下来跟他谈话时他这样告诉我。
It provided an implementation of remote session beans directly and used Castor for its implementation of container-managed persistence (CMP) entity beans.
它直接提供了一个远程会话bean的实现，并使用Castor作为它的容器管理持久性(CMP)实体bean的实现。
If referential integrity violations are discovered during the load test, then you might also need to set the sequence grouping for container managed persistence.
如果在负载测试过程中发现存在引用完整性违规，则可能还需要为容器管理的持久性设置顺序分组。
For example, if the mapping attribute of the DataSource object is not set, the data source might not act as the data source in the container-managed persistence (CMP).
例如，如果未设置DataSource对象的mapping属性，则数据源的行为方式不会与容器管理的持久性(CMP)中的数据源相同。
The embedded transaction container requires that a specific data source, TxnDataSource, is used when connecting to the database for container Managed Persistence (CMP).
在连接ContainerManaged Persistence (CMP)的数据库时，嵌入式事务容器要求使用一个特定的数据源txndatasource。
It appeared to us that a managed persistence solution was not required for our programming model, and we wanted to unleash the power of SQL without hiding it from the developer.
显然，对于我们的编程模型，受管持久性解决方案不是必需的，我们希望释放出SQL的威力，而不是对开发人员隐藏它。
However, this choice can be limited by the deployment tool's limitation to map the bean instance's state to the database, in which case a bean-managed persistence (BMP) entity bean may be used.
但是，这个选择会受到部署工具局限性的限制—部署工具将bean实例的状态映射到数据库，这种情况下可能会使用bean管理的持久性(BMP)实体bean。
Compared with flow-managed persistence in atomic flows, the most significant change happens to the scope of transactions: atomicity applies to each step of the process rather than the entire flow.
与原子流中流管理的持久化相比，事务作用域发生的最大变化时：原子性应用于进程的每一步而不是整个流。
It's because the JPA specification imposes a group-like behavior on the managed instances of a persistence context.
这是因为JPA规范对持久性上下文的管理实例施加的了一个类似组的行为。
The resource manager implements the object pool and it gets the managed resource that implements persistence, security state management, and transaction.
资源管理器实现了对象池，它能够获得实现持久化、安全性状态管理和事务的托管资源模式。
应用推荐