Listing 1. Transparent resource enlistment with bean-managed transactions.
清单1.bean管理的事务的透明资源征用。
It's impossible to overemphasize the importance of container-managed transactions.
对容器管理的事务怎么强调都不会过分。
As you can see, the MDB Bean type is message-driven, and the EJB USES container managed transactions.
可以看到，MDBBean类型是消息驱动的，并且EJB使用容器管理的事务。
The stub and skeleton objects also take care of beginning and committing container-managed transactions.
存根和骨架对象还负责开始和提交容器管理的事务。
Bean-managed transactions are started and ended explicitly by a component using the UserTransaction class.
Bean管理的事务是由组件使用usertransaction类显式启动和结束的。
In the case of J2EE container-managed transactions, the container takes responsibility for determining transaction bounds.
在J2EE容器管理事务的情况下，容器的职责是确定事务范围。
If bean-managed transactions are employed, the developer will determine under what conditions a transaction should begin and end.
如果使用的是bean管理的事务，那么开发人员将确定事务的开始条件和结束条件。
This returns true if the MDB is using container-managed transactions and the method in question has a transaction attribute of Required.
如果MDB正在使用容器托管的事务，而且要处理的方法具有Required事务属性，那么isDeliveryTransacted会返回true。
If the transaction attribute takes the other allowed value of NotSupported, or the MDB is using bean-managed transactions, then it returns false.
如果事务属性采用NotSupported允许的其他值，或者MDB正在使用bean托管的事务，则返回false。
The EJB container provides full transactional support for global transactions, including container managed transactions (CMT) and bean managed transactions.
ejb容器提供对全局事务的充分的事务支持，包括容器管理事务(CMT)和Bean管理事务。
Suppose you take the EJB from Listing 1 and deploy it using container-managed transactions and a transactional attribute of RequiresNew for the business method.
假定取用清单1中的EJB，并用容器托管的事务部署它，将业务方法的事务属性设定为RequiresNew。
The EJB container provides full transactional support for global transactions, including container managed transactions (CMT) and bean managed transactions (BMT).
EJB容器提供对全局事务的完整事务支持，包括容器管理的事务 (CMT)和Bean 管理的事务 (BMT)。
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容器中容器管理的事务不使用该属性。
As entity beans must always use container-managed transactions, only session beans or message-driven beans with bean-managed transactions are allowed to invoke this method.
因为实体bean必须使用容器管理事务，所以只有使用bean管理事务的会话bean和消息驱动bean才能调用该方法。
The EJB container in WebSphere Application Server is ideally suited to the deployment of transactional components, and provides support for both container and bean managed transactions.
WebSphereApplicationServer 中的EJB容器完美地适合于事务组件的部署，并且提供对容器和bean管理事务两者的支持。
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.
使用容器管理的事务（CMT）提供了两个关键的优势（如果没有容器支持这几乎是不可能的）：可组合的工作单元和健壮的事务行为。
This can happen for servlets, session beans using bean-managed-transactions, and a few other scenarios.
使用bean 管理事务的会话bean 及一些其它场景可能发生这种情况。
This can happen for servlets, session beans using bean-managed-transactions, and a few other scenarios.
使用bean 管理事务的会话bean 及一些其它场景可能发生这种情况。
应用推荐