全部

1·Continuing with this design, you can place all of the business logic and transition mapping in a utility class for use by both our controller and JSPs.

继续这个设计，您可以将所有的业务逻辑和转换映射放在一个实用程序类中，以供我们的控制器和JSP使用。

2·Model refers to your data, View to your presentation layer, and Controller refers to the application or business logic.

模型指数据，视图指表示层，而控制器指应用程序逻辑或业务逻辑。

3·One controller can be assigned to several business components.

一个控制器可以分配给多个业务组件。

4·The controller layer is responsible for implementing the business logic of the service, achieved by invoking other services, other controllers, or an entity management layer.

控制器层负责实现服务的业务逻辑，具体通过调用其他服务、其他控制器或实体管理层实现。

5·Decoupling the service definition from the business logic (controller) and from access to the data (entity) ensures that no business logic manifests itself in the entities.

将服务定义同业务逻辑(控制器)以及数据(实体)访问分离，可确保实体中不会透露任何业务逻辑。

6·The idea is to keep the controller class as simple as possible to allow business logic to be abstracted to a helper class.

这个想法是为了使控制器类尽可能保持简单以允许业务逻辑被抽象为助手类。

7·To cover the business rules identified in the sections above, the controller component clamps together all of these components.

为实现上一节所讲的业务规则，通过一个控制器组件将服务器内的所有组件紧紧联系在一起。

8·This is a controller class that has the responsibility of managing the execution of the business logic.

这是一个控制器类，其职责是管理业务逻辑的执行。

9·For now, a controller class is a placeholder for one or more classes that would be fleshed out during design to implement the business logic of your system.

现在，控制器类是设计实现系统商业逻辑填充的一个或多个类的位置保持器。

10·The most common mistake I see is business process in the controller.

我所见到的一个最普遍的错误就是将业务处理放置在了控制器当中。