Most of the transaction pitfalls discussed in this series' first article are associated with the Declarative transaction model.
本系列的第一篇文章所讨论的大多数事务陷阱都与Declarative Transaction模型相关。
The container will not automatically roll back a transaction on a checked exception when you use the Declarative Transaction model.
在使用Declarative Transaction 模型时，容器将不会针对检测到的异常自动回滚事务。
If you use Spring 2.5 with WebSphere Application Server V6.0.2.19 or V6.1.0.9 or later, you can take advantage of full support for Spring's declarative transaction model.
如果将Spring 2.5与WebSphereApplicationServerV6.0.2.19或V6.1.0.9或者更高版本一起使用，则可以利用对Spring的声明式事务模型的完全支持。
Because you cannot programmatically pass a transaction context, the API layer must use the declarative transaction model, meaning that the container manages the transaction.
由于您不能通过编程传递事务上下文，因此 API层必须使用声明式事务模型，这表示容器将管理事务。
Suppose you want to stick with using the Declarative transaction model to simplify the transaction processing but still increase throughput during a high-user-concurrency scenario.
假设您希望坚持使用Declarative Transaction模型来简化事务处理，但是仍然能在高用户并发性场景中增加吞吐量。
But as you will see in this article, the term declarative transactions describes a transaction model, but by no means is it a transaction strategy.
在本文中，术语声明式事务描述的是一个事务模型，但它绝不是一种事务策略。
But as you will see in this article, the term declarative transactions describes a transaction model, but by no means is it a transaction strategy.
在本文中，术语声明式事务描述的是一个事务模型，但它绝不是一种事务策略。
应用推荐