这在松散意义上称为关注点分离。
关注点分离指把代码提取到不同的层
Separation of concerns refers to extracting the code into various layers
这篇教程将展示关注点分离的两个实现。
This tutorial will demonstrate two implementations of this separation of concerns.
最后，委派逻辑通常会得到更干净的关注点分离。
Finally, delegating logic often leads to a cleaner separation of concerns.
因此，关注点分离的概念是定义集成服务的基础。
As a result, the concept of separation of concerns is the foundation to the definition of the integration services.
关注点分离简化了集成体系结构的实现。
Separation of concerns simplifies integration architecture implementation.
关注点分离和配置文件。
在架构构建块职责之间可以实现一个清晰的关注点分离。
Achieve a clear separation of concerns between architectural building block responsibilities.
通过关注点分离，可以将集成需求分解为更细粒度的服务。
Through separation of concerns, integration requirements are decomposed into more granular services.
注重关注点分离，即使两个关注点的初始大小差别很大。
Respecting separation of concerns, even if initial size of the two concerns is rather unequal.
将应用程序划分为层，这是一种在体系结构中关注点分离的基本技术。
Dividing the application into tiers (or layers) is an essential technique for separating concerns within the architecture.
业务集成得益于强制关注点分离集成数据和应用程序以满足业务要求。
Business integration benefits from an enforcement of separation of concerns to integrate data and applications as appropriate for business needs.
这意味着需要保持关注点分离，并且需要在部署单元内像调用一样分组。
This implies that you need to maintain separation of concerns and to group like calls within a deployment unit.
您还了解了如何使用关注点分离和最佳重用的设计模式构造Web应用程序。
You have also seen how to construct the Web application using design patterns for separation of concerns and better reuse.
关注点分离是实现具有良好结构的代码的基础，它封装了责任和依赖关系。
Separation of concerns is fundamental to well-structured code, because it encapsulates responsibilities and dependencies.
与大部分动态Web应用程序一样，Web服务可以从多层架构的关注点分离中受益。
Web services can benefit from the separation of concerns inherent in a multi-tier architecture in much the same way as most dynamic Web applications.
它提高了我们对于一个设计良好的、可维护的软件系统所需的、关注点分离的表达能力。
It enhances our ability to express the separation of concerns necessary for a well-designed, maintainable software system.
图1显示了开发工作站和最终生产环境之间的代码流，我们以此来说明关注点分离的概念。
Figure 1 illustrates the separation of concerns concept by showing the flow of code between the development workstation to final production.
这样避免了把类搞乱，确保了关注点分离并且提供了与未来相关Roo附加组件的兼容性。
This reduces the clutter in a class, ensures separation of concerns and offers compatibility with future versions of the relevant Roo add-ons.
我们所指的关注点分离阶段是指使用不同的环境控制组成部署发布版本的代码流和其他文件。
By the phrase separation of concerns we mean the use of different environments to control the flow of code and other files that make up a deployment release.
应用这一体系结构并结合“关注点分离”概念，是替换传统集成方法的一种完美选择。
Applying this architecture and using the concepts of "separation of concerns" provides a clear alternative to traditional integration approaches.
实际上，除了规模大小有区别外，面向对象语言中对象之间的关注点分离与模块化的概念基本一致。
In fact, the kind of separation of concerns between objects in an OO language is much the same concept as for modules, except on a larger scale.
和这个关注点分离允许编译器来实现更多的策略在未来如果检测到其他模式之间的比较值。
And this separation of concerns allows the compiler to implement even more strategies in the future if other patterns among the comparison values are detected.
在理想情况下，每个功能区(如流程服务)都是“纯”功能区，为了实现关注点分离仅提供了一个服务类。
In an ideal world, each functional area such as process services, would be "pure", offering only one class of services in order to provide a separation of concerns.
关注点分离建议将业务需求分解为多个服务；合并表示业务流程的现有服务以及新的服务的组合。
Separation of concerns suggests decomposing business needs into services; and composing combinations of existing and new services that represent business processes.
这种方法基于的是关注点分离和完善迭代信息的原则，但主要还是从多个特定视角去挖掘统一模型。
This approach is based on the principles of separation of concerns, refining iterative information but mainly on the exploitation of multiple specialized representations of the same model.
它们提供强大的(但又容易被忽视的)xml处理方法。这种方法有3个杰出的优点：可重用性强、可读性强，以及关注点分离。
They provide a powerful and often overlooked means of processing XML with three distinct advantages: reusability, easier readability, and a separation of concerns.
在构建优秀的OO设计时，必须考虑称为关注点分离(SeparationofConcerns,soc)的概念。
When building good oo designs, it's necessary to think about a concept called Separation of Concerns (SoC).
其主要目标是在保持关注点分离的同时，为构建企业集成解决方案提供一个简单的模型，该模型对产出可维护、可测试的代码来说是必不可少的。
Its primary goal is to provide a simple model for building enterprise integration solutions while maintaining the separation of concerns that is essential for producing maintainable, testable code.
通过相互分离接口保持关注点的分离。
Keep separation of concerns by separating the interfaces from each other.
应用推荐