最后，委派逻辑通常会得到更干净的关注点分离。
Finally, delegating logic often leads to a cleaner separation of concerns.
在架构构建块职责之间可以实现一个清晰的关注点分离。
Achieve a clear separation of concerns between architectural building block responsibilities.
与大部分动态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.
我们所指的关注点分离阶段是指使用不同的环境控制组成部署发布版本的代码流和其他文件。
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.
实际上，除了规模大小有区别外，面向对象语言中对象之间的关注点分离与模块化的概念基本一致。
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.
通过相互分离接口保持关注点的分离。
Keep separation of concerns by separating the interfaces from each other.
这是在JSF中分离关注点的另一个例子。
This is another example of the separation of concerns in JSF.
您可以看见它们都遵守了分离关注点原则，因为每个组件处理一个单独的调用来检索相关的对象。
You can see that the separation of concern rule is obeyed, as every component handles an isolated call to retrieve its related object.
MVC模式天生就是可测试的，而且鼓励对关注点的分离。
By nature, the MVC pattern is highly testable and encourages good separation of concerns.
将应用程序划分为层，这是一种在体系结构中关注点分离的基本技术。
Dividing the application into tiers (or layers) is an essential technique for separating concerns within the architecture.
通过关注点分离，可以将集成需求分解为更细粒度的服务。
Through separation of concerns, integration requirements are decomposed into more granular services.
这条设计原则非常类似敏捷经常用在软件开发中的设计原则(分离关注点，避免浪费等)。
This design principle is very similar to agile design principles (separation of concerns, avoid waste etc.) that are often used in software development.
ESB的关键特性是分离关注点。
您还了解了如何使用关注点分离和最佳重用的设计模式构造Web应用程序。
You have also seen how to construct the Web application using design patterns for separation of concerns and better reuse.
这样避免了把类搞乱，确保了关注点分离并且提供了与未来相关Roo附加组件的兼容性。
This reduces the clutter in a class, ensures separation of concerns and offers compatibility with future versions of the relevant Roo add-ons.
关注点分离指把代码提取到不同的层
Separation of concerns refers to extracting the code into various layers
在视图中使用XQuery 并在数据中使用XML 是分离关注点的更好方式。
XQuery as the view used in conjunction with XML as the data represents an even better way to split the concerns.
但它是分离关注点的关键，我们在这些专栏中讨论过这个问题。
But that is the whole point of separation of concerns that we have discussed throughout these columns.
我经常使用这种模式，并发现借助它可以更好地分离组件之间的关注点。
I use this pattern frequently and find that it helps me better separate the concerns between the components.
这篇教程将展示关注点分离的两个实现。
This tutorial will demonstrate two implementations of this separation of concerns.
可以利用这种关注点的分离分别测试横切规范及它们的行为。
You can leverage this separation of concerns to test their behavior separately from the crosscutting specification.
这种方法是分离关注点原则的一个变种，附在模型-视图-控制器架构中。
This approach is a variation of the separation of concerns principle embodied in the Model-View-Controller architecture.
图1显示了开发工作站和最终生产环境之间的代码流，我们以此来说明关注点分离的概念。
Figure 1 illustrates the separation of concerns concept by showing the flow of code between the development workstation to final production.
如果目的是分离关注点、透明性和灵活性，那么面向方面的编程 (AOP)通常就是正确的答案。
When you're aiming for separation of concerns, transparency, and flexibility, aspect-oriented programming (AOP) is often the right answer.
MVC最重要的就是合理的分离关注点。
一种用于构造服务组件的简单方法，关注于业务功能并使基础设施关注点保持很好的分离。
A simple approach to the construction of service components, concentrating on business function and keeping infrastructure concerns well separated.
应用这一体系结构并结合“关注点分离”概念，是替换传统集成方法的一种完美选择。
Applying this architecture and using the concepts of "separation of concerns" provides a clear alternative to traditional integration approaches.
此图强调中介(用于服务公开)和提供者创建都对服务实现有贡献，但是由于关注点隔离的要求，它们在架构上是分离的。
The figure emphasizes that mediation (for service exposure) and provider creation contribute to service realization, but they are architecturally distinct due to separation of concerns.
它提高了我们对于一个设计良好的、可维护的软件系统所需的、关注点分离的表达能力。
It enhances our ability to express the separation of concerns necessary for a well-designed, maintainable software system.
这种方法基于的是关注点分离和完善迭代信息的原则，但主要还是从多个特定视角去挖掘统一模型。
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.
应用推荐