The flow-scoped persistence context.
流作用域的持久化上下文。
Persistence context scoped to each invocation.
作用域为每个调用的持久化上下文。
Persistence context scoped to a database transaction.
持久化上下文作用域划定到数据库事务。
Types of persistence context: Transaction or extended.
持久化上下文的类型：事务性或扩展型。
Persistence programming without the flow-scoped persistence context.
不使用流作用域持久化上下文的持久化编程。
It will then commit the transaction, unbind the persistence context, and close it.
然后提交事务，取消绑定持久化上下文并关闭它。
In this case, the FlushMode of the flow-scoped persistence context will always be AUTO.
在这种情况下，流作用域持久化上下文的FlushMode将一直是AUTO。
Within the persistence context, the entity instances and their lifecycles are managed.
在永久性上下文中，实体实例及其生命周期得到管理。
Merge : Update the current persistence context with the current state of the given entity.
merge：修改当前持久化环境的指定实体的当前状态。
To understand the difference, you must first understand what a persistence context means.
若要了解它们之间的区别，您必须首先了解持久性上下文的含义。
You have to use this default setting when programming with a flow-scoped persistence context.
在用流作用域的持久化上下文编程时必须使用此默认设置。
The booking entities managed by one persistence context are detached from the perspective of the other.
一个持久化上下文管理的booking实体，从另一个持久化上下文的角度来看，是分离的。
It's because the JPA specification imposes a group-like behavior on the managed instances of a persistence context.
这是因为JPA规范对持久性上下文的管理实例施加的了一个类似组的行为。
Within the persistence context, the entity's association with the underlying persistence store is managed by the entity manager (EM).
在持久性上下文中，实体与基础持久性存储区的关联由实体管理器(entity manager, EM)管理。
When the action method is invoked, it is necessary to reattach the updated object to the persistence context, making the changes permanent.
当调用该操作方法时，必须重新使已更新的对象与持久化上下文建立联系。
Additionally, this interceptor needs to be registered in the persistence context of JPA by means of the hibernate.ejb.interceptor property.
此外，还需要通过hibernate .ejb . interceptor属性将拦截器注册到JPA的持久性上下文中。
Programming persistence in Web flows without the flow-scoped persistence context object is still feasible but incurs many hurdles and pitfalls.
不使用流作用域持久化上下文对象的web流中的持久化编程也是可行的，只是有很多障碍和缺陷。
It's clear that the flow-scoped persistence context makes persistence programming in both atomic and non-atomic Web flows smoother and simpler.
显然流作用域持久化上下文使原子和非原子we b流中的持久化编程更顺利、更简单。
readOnly: Setting up a read/write transaction by specifying @Transactional(readOnly=false) will make the FlushMode of the persistence context AUTO.
readOnly：通过指定 @Transactional(readOnly=false)建立读/写事务，这样会使持久化上下文的FlushMode 变为AUTO。
Because the application uses a stateless service interface, the course instance is at this point considered "detatched" from the persistence context.
因为应用程序使用无状态的服务接口，所以此时的课程实例看作已经与持久化上下文 “分离”。
A data access object (DAO) that USES JPA is packaged with a persistence.xml that defines persistence context for the JPA EntityManager used by the application.
使用JPA的数据访问对象(DAO)与persistence . xml打包在一起，后者为应用程序使用的JPAEntityManager定义持久性上下文。
The @PersistenceContext annotation has an optional attribute type, which defaults to PersistenceContextType.TRANSACTION (that is, a transaction-bound persistence context).
@PersistenceContext注释有一个可选的属性type，该属性默认为 PersistenceContextType.TRANSACTION（也就是绑定到事务的持久化上下文）。
This was a difficult integration task for us, and exposed several subtle issues that were difficult to address like exception handling, concurrency, security, and persistence context management.
这对我们来说是一项艰巨的集成任务，而且曝露了不少难以解决的微妙问题，比如异常处理、并发性、安全性、以及持久性上下文管理。
The flow-scoped persistence-context object manages data loaded during the flow as persistent entities, and data changes cached as the entities' dirty states.
流作用域的持久化上下文对象将流期间加载的数据作为持久化实体来管理并将数据变更缓存为实体的脏状态。
Disk-offload, context persistence, and cluster failures
磁盘分流、上下文持久性和集群故障
Future releases of Fabric will likely mitigate this risk, perhaps with full context persistence.
将来的Fabric版本可能会缓解此风险，也许是使用完全上下文持久性。
Castor's persistence operations take place within the context of a transaction.
Castor的持久性操作在事务上下文内进行。
A downside of the Open Session in View pattern is that the persistence-context object is effectively scoped to a user request.
OpenSessioninView模式的一个缺点是持久化上下文对象被高效地划定到用户请求作用域内。
The same persistence-context object is reused during the course of the entire flow, eliminating detached-entity state and the corresponding LazyInitializationException.
在整个流过程中都重用同一个持久化-上下文对象，这避免了分离实体状态的问题和相应的LazyInitializationException 异常。
The interesting part (at least in this context) is that underneath it uses Subversion to provide persistence.
有趣的地方（至少对于本文来说）在于底层使用Subversion来提供持久性。
应用推荐