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层和客户端编排策略事务策略是应用于大多数标准业务应用程序的核心策略。
Some transactions might start in the API layer, some in the business layer, and some even in the DAO layer.
一些事务可能在API层中开始，一些在业务层中开始，还有一些甚至在DAO 层中开始。
The API Layer transaction strategy will work fine for most business applications.
API Layer事务策略将良好地应用于大多数业务应用程序。
Therefore, avoid any reference to servlet API or Struts API calls in the business layer.
因此，应该避免在业务逻辑层使用对servletAPI或Struts API调用的任何引用。
It consists of four loosely-coupled bundles: a Web layer, a business logic layer, a persistence layer, and an API bundle.
该架构包含4个松耦合bundle：一个web层、一个业务逻辑层、一个持久化层、以及一个APIbundle。
It consists of four loosely-coupled bundles: a Web layer, a business logic layer, a persistence layer, and an API bundle.
该架构包含4个松耦合bundle：一个web层、一个业务逻辑层、一个持久化层、以及一个APIbundle。
应用推荐