The API Layer and Client Orchestration transaction strategies that I've covered in previous articles in this series are core strategies that apply to most standard business applications.
我在本系列的前几篇文章中所介绍的api层和客户端编排策略事务策略是应用于大多数标准业务应用程序的核心策略。
The main purpose of the consumer layer is to gather all the information required to be able to start a business process or transaction.
使用者层的主要目的是，收集所需的所有信息，以便能启动业务流程或事务。
If a stateful solution is essential, consider using stateless session beans with a simple transaction layer, or creating a thin servlet layer on top of the business tier.
如果有状态解决方案是必需的，则请考虑使用带有简单事务层的无状态会话bean，或者在业务层上创建瘦servlet层。
The exception to this rule is if the client business delegate in the client layer controlling the transaction scope is managed as a Spring bean by the Spring Framework.
此规则的例外情况是，管理事务作用域的客户端层中的客户端业务代理由SpringFramework托管为Springbean。
The API Layer transaction strategy will work fine for most business applications.
APILayer事务策略将良好地应用于大多数业务应用程序。
The API Layer transaction strategy will work fine for most business applications.
APILayer事务策略将良好地应用于大多数业务应用程序。
应用推荐