The most common container-managed transaction attribute is Required.
最常用的容器管理的事务属性是Required。
The example code in Listing 1 demonstrates a bean-managed transaction (sometimes called a programmatic transaction.)
清单1中的示例代码演示了bean 管理的事务（有时也称为 编程（programmatic）事务）。
In the case of a J2EE bean-managed transaction, the bean is completely responsible for controlling transaction boundaries.
在J2EEbean管理事务的情况下，bean负责控制事务范围。
For all the transactional RPCs, you can use either container-managed transaction demarcation or component-managed transaction demarcation.
对于所有事务的RPC，您可以使用容器管理的事务划分或者组件管理的事务划分。
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.
这意味着可以在同一个事务工作单元中进行发送和接收，而无需借助于bean或者容器管理的事务。
Listing 2 is a sample of how a business method can be implemented in case of a bean-managed transaction (note that exceptions handling is omitted for simplicity)?
清单2示例展示了业务方法在bean管理事务的情况下是如何实现的(注意，为简化起见省略了异常处理)？
There are, however, no container managed transaction services provided by the Web container, although applications can programmatically control the transaction scope if desired.
然而，Web容器不提供容器管理的事务服务，但是如果需要，可以通过应用程序以编程方式来控制事务范围。
There are, however, no container managed transaction services provided by the Web container, although applications can programmatically control the transaction scope if desired.
然而，Web容器不提供容器管理的事务服务，但是如果需要，可以通过应用程序以编程方式来控制事务范围。
应用推荐