对容器管理的事务怎么强调都不会过分。
It's impossible to overemphasize the importance of container-managed transactions.
存根和骨架对象还负责开始和提交容器管理的事务。
The stub and skeleton objects also take care of beginning and committing container-managed transactions.
最常用的容器管理的事务属性是Required。
The most common container-managed transaction attribute is Required.
可以看到，MDBBean类型是消息驱动的，并且EJB使用容器管理的事务。
As you can see, the MDB Bean type is message-driven, and the EJB USES container managed transactions.
对于所有事务的RPC，您可以使用容器管理的事务划分或者组件管理的事务划分。
For all the transactional RPCs, you can use either container-managed transaction demarcation or component-managed transaction demarcation.
JobStoreCMT要求(二)数据源包含连接，不会的一部分容器管理的事务。
JobStoreCMT requires a (second) datasource that contains connections that will not be part of container-managed transactions.
这意味着可以在同一个事务工作单元中进行发送和接收，而无需借助于bean或者容器管理的事务。
This means that you can perform the send and receive as part of the same transactional unit of work without resorting to a bean- or container-managed transaction.
在交互完成后，所有的容器管理事务被自动提交，因此在web容器中容器管理的事务不使用该属性。
All container managed transactions are auto-committed after the interaction completes, and so this attribute is not used by container managed transactions in the Web container.
然而，Web容器不提供容器管理的事务服务，但是如果需要，可以通过应用程序以编程方式来控制事务范围。
There are, however, no container managed transaction services provided by the Web container, although applications can programmatically control the transaction scope if desired.
而且，当您想在单一事务环境下将Encina与另一xa相应的资源管理器相连接，那么就必须使用容器管理的事务。
Also, when you want to make connections to Encina and another XA compliant resource manager within a single transactional context, container-managed transactions must be used.
EJB容器提供对全局事务的完整事务支持，包括容器管理的事务 (CMT)和Bean 管理的事务 (BMT)。
The EJB container provides full transactional support for global transactions, including container managed transactions (CMT) and bean managed transactions (BMT).
使用容器管理的事务（CMT）提供了两个关键的优势（如果没有容器支持这几乎是不可能的）：可组合的工作单元和健壮的事务行为。
Using container-managed transactions (CMTs) provides two key advantages that are nearly impossible to obtain without container support: composable units of work, and robust transactional behavior.
通过将transaction - type属性设置为Container或bean您可以指出EJB组件是使用bean管理的事务性支持还是容器管理的事务性支持。
You indicate whether an EJB component USES bean-managed or container-managed transactional support by setting the transaction-type attribute to either container or bean.
在这两种情况下，容器管理事务并确定是否应该提交给定的事务。
In both cases, the container manages the transactions and determines whether or not a given transaction should be committed.
这两种情况中，都是容器管理事务，并确定应该提交给定的事务还是应该回滚它。
In both cases, the container manages the transactions and determines whether or not a given transaction should be committed or rolled-back.
EJ b容器支持的事务管理也可以影响性能。
Transaction management supported by the EJB container can also affect performance.
ejb容器使开发人员不必管理常见的企业功能，如安全性、事务处理、连接合用和外部资源管理。
The EJB container relieves developers from managing common enterprise functions such as security, transaction handling, connection pooling, and external resource management.
在J2EE容器管理事务的情况下，容器的职责是确定事务范围。
In the case of J2EE container-managed transactions, the container takes responsibility for determining transaction bounds.
该容器为管理资源、事务和并行性之类的内容提供了自动支持，但是也会为应用程序引入大量负载负荷。
The container provides automatic support for managing things like resources, transactions, and concurrency but can also introduce substantial overhead in your applications.
在LocalTransaction模型中，事务由底层数据库资源管理程序(而非应用程序所在的容器或框架)管理，这便是它得名的原因。
The Local transaction model gets its name from the fact that transactions are managed by the underlying database resource manager, not the container or framework your application is running in.
Web服务的生成会自动地生成eJB组件，这个组件可以用来管理由ejb容器执行的事务。
Generating the web service automatically generates the EJB component, which can be used to manage transactions that are performed by the EJB container.
它利用Blueprint容器的功能来管理持久性上下文和全局事务，以确保业务逻辑的开发和单元测试尽可能保持简单。
It leverages the Blueprint container's ability to manage both persistence contexts and global transactions to ensure the business logic remains as simple as possible to develop and unit test.
即使合作e JB存在于不同的容器中，CORBAOTS也可以启用容器的事务管理程序进行协调，从而使事务跨容器传播。
Even if the collaborating EJBs are in different containers, CORBA OTS enables the containers' transaction managers to coordinate so that the transaction propagates across containers.
本地事务(有时称为数据库事务)是由数据库而不是容器环境管理的事务。
Local transactions (sometimes referred to as database transactions) are transactions that are managed by the database rather than the container environment.
实体管理层负责实体管理，并确保容器内该对象的事务完整性。
The entity management layer is responsible for entity management and ensuring the transaction integrity of that object within the container.
通过允许COM +容器对其进行管理，COM +组件可以参与事务以及使用由COM +容器提供的其他服务。
By allowing the com + container to manage it, the com + component can participate in transactions and use other services provided by the com + container.
当一个容器中的ejb调用另一个容器中的EJB时，事务管理程序将使用CORBAOTS。
The transaction manager USES CORBA OTS when an EJB in one container calls an EJB in another container.
如果您未使用此注释，则容器将假定您使用声明式事务管理(CONTAINER)，它是EJB 3.0的默认事务类型。
If you don't use this annotation, the container assumes you are using declarative transaction management (container), which is the default transaction type for EJB 3.0.
为了控制事务组件的行为，ejb容器提供了一组用于控制容器管理组件的事务行为的属性。
In order to control the behavior of transactional components, the EJB container offers a set of attributes that can be used to control the transactional behavior of container managed components.
例如，它可能使用Supports的容器管理器事务属性来调用消息驱动bean (MDB)。
For example, it might invoke a message-driven bean (MDB) with a container manager transaction attribute of Supports.
应用推荐