对于我们来说，实体管理增加了一层不必要的开销，并且对性能有负面的影响。
For us, entity management adds a layer of overhead that we do not require and which can negatively affect performance.
另一种限制源自于这样一个事实：域对象可以通过由实体管理器所管理的域对象所在的层访问，也可以通过分离它的所有其他层访问。
Another restriction arises from the fact that the domain objects can be accessed both in the tier where they are managed by the entity manager and in all the other tiers where they are detached.
控制器层负责实现服务的业务逻辑，具体通过调用其他服务、其他控制器或实体管理层实现。
The controller layer is responsible for implementing the business logic of the service, achieved by invoking other services, other controllers, or an entity management layer.
逻辑卷管理是一个磁盘抽象层，它可以将多个物理磁盘分组成称为卷组(volumegroup)的单一实体。
Logical volume management is a disk abstraction layer that allows you to group physical disks into a single entity called a volume group.
无论是否在实体管理器中，它们都应该准备好在任何层中调用。
They should be ready for invocation in any tier, whether within the realm of the entity manager or not.
通过这种方法，JPA实体会在一个地方进行管理，并且可以作为数据层由许多项目使用，而不是包含JPA实体和管理豆的项目使用。
That way, JPA entities are managed in one place and can be used as a data layer by many projects, rather than each project containing its own JPA entities and manager beans.
实体管理层负责实体管理，并确保容器内该对象的事务完整性。
The entity management layer is responsible for entity management and ensuring the transaction integrity of that object within the container.
当域对象离开数据访问层时，它与实体管理器脱离。
When a domain object leaves the data access tier, it gets detached from the entity manager.
采用元数据组织管理的三层体系结构：元数据子集、元数据实体和元数据元素。
The three metadata structure of organizational management was adopted: metadata section, metadata entity, and metadata element.
业务实体层持久化并管理工作流对象。
Business entity layer stored and maintained business object.
业务实体层持久化并管理工作流对象。
Business entity layer stored and maintained business object.
应用推荐