This is known as a container managed entity manager.
这就是所谓的容器管理的实体管理器。
EJB finders can be defined on a container managed entity bean using the EJB Visual editor.
EJB查询工具能通过EJBVisual编辑器定义在容器管理的实体bean中。
This does not mean that application-managed entity managers cannot be configured as JTA entity managers.
这并不意味着不能将应用程序管理的实体管理器配置为JTA 实体管理器。
However, JPA defines the notion of container-managed entity manager versus application-managed entity manager.
然而，jpa定义了容器管理的实体管理器与应用程序管理的实体管理器的概念。
Because the Employee object is a managed entity, updating the object automatically updates it in the grid partition.
由于Employee对象是托管实体，因此更新某个对象也会自动在网格分区中更新该对象。
This problem is not limited to the use of container-managed entity beans but is general to the object-oriented approach.
该问题不是仅限于容器管理的实体bean的使用中，而是普遍存在于面向对象方法中。
Each managed entity (which could be the entire application or a service within the application) instantiates an MBean and registers it using a human-readable name.
每个受管的实体(可能是整个应用程序或应用程序中的服务)实例化一个MBean并用可读懂的名称注册它。
WebSphere application Server V6.1 and later supports JPA application-managed entity managers, which might have a transaction type of either JTA or resource-local.
WebSphereApplicationServerV6.1及更高版本支持JPA应用程序托管的实体管理器，该管理器可能是JTA或本地资源事务类型。
The keys "name" and "type" are commonly used, and when present, the name should uniquely identify the managed entity across all MBeans of that type within that domain.
“name”和 “type” 这两个键是常用的，在使用的时候，name应当在域中所有的同类 MBean中能够唯一地标识受管实体。
In the JEST context, the resource - the central concept of a RESTful architecture - is a customizable persistent closure of an identifiable, managed entity, as illustrated in Figure 3.
在JEST环境中，资源—RESTful架构的中心概念—是一个可识别和管理的实体的一种可定制的持久化闭包，如图3所示。
In the JEST context, the resource - the central concept of a RESTful architecture - is a customizable persistent closure of an identifiable, managed entity, as illustrated in Figure 3.
在JEST环境中，资源—RESTful架构的中心概念—是一个可识别和管理的实体的一种可定制的持久化闭包，如图3所示。
应用推荐