ESB的关键特性是分离关注点。
MVC最重要的就是合理的分离关注点。
进一步在应用开发和操作性任务间分离关注点
to further address the separation of concern between application development and operational tasks
这是在JSF中分离关注点的另一个例子。
This is another example of the separation of concerns in JSF.
但它是分离关注点的关键，我们在这些专栏中讨论过这个问题。
But that is the whole point of separation of concerns that we have discussed throughout these columns.
这种方法是分离关注点原则的一个变种，附在模型-视图-控制器架构中。
This approach is a variation of the separation of concerns principle embodied in the Model-View-Controller architecture.
因为服务是一个分离关注点，建议你把服务代码放到它自己的文件里。
Given that the service is a separate concern, we suggest that you write the service code in its own file.
在视图中使用XQuery 并在数据中使用XML 是分离关注点的更好方式。
XQuery as the view used in conjunction with XML as the data represents an even better way to split the concerns.
这条设计原则非常类似敏捷经常用在软件开发中的设计原则(分离关注点，避免浪费等)。
This design principle is very similar to agile design principles (separation of concerns, avoid waste etc.) that are often used in software development.
您可以看见它们都遵守了分离关注点原则，因为每个组件处理一个单独的调用来检索相关的对象。
You can see that the separation of concern rule is obeyed, as every component handles an isolated call to retrieve its related object.
第2部分介绍了利用ID - lists模式减少远程调用的数量，并且还遵守分离关注点模式。
Part 2 introduced the ID-lists pattern to reduce the number of remote calls and still obey the separation of concerns pattern.
如果目的是分离关注点、透明性和灵活性，那么面向方面的编程 (AOP)通常就是正确的答案。
When you're aiming for separation of concerns, transparency, and flexibility, aspect-oriented programming (AOP) is often the right answer.
Bejeck在文章中试图创建混合了继承和组合关系的组件，实施分离关注点，尤其是分离视图和商业逻辑。
In the article Bejeck is trying to create components with a mixture of inheritance and composition, and enforce separation of concerns, especially between view and business logic.
ESB提供了一个层次，在这一层次中，服务请求者和服务提供者之间的关系是间接的和分离的，这使得可以更好地分离关注点。
The ESB provides a level of indirection and decoupling between service requestors and service providers that enables better separation of concerns.
ESB提供了一个层次，在这一层次中，服务请求程序和服务提供程序之间的关系是间接的和分离的，这使得可以更好地分离关注点。
An ESB provides a level of indirection and decoupling between service requesters and service providers that enables better separation of concerns.
我经常使用这种模式，并发现借助它可以更好地分离组件之间的关注点。
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.
通过相互分离接口保持关注点的分离。
Keep separation of concerns by separating the interfaces from each other.
可以利用这种关注点的分离分别测试横切规范及它们的行为。
You can leverage this separation of concerns to test their behavior separately from the crosscutting specification.
图1显示了开发工作站和最终生产环境之间的代码流，我们以此来说明关注点分离的概念。
Figure 1 illustrates the separation of concerns concept by showing the flow of code between the development workstation to final production.
这意味着需要保持关注点分离，并且需要在部署单元内像调用一样分组。
This implies that you need to maintain separation of concerns and to group like calls within a deployment unit.
最后，委派逻辑通常会得到更干净的关注点分离。
Finally, delegating logic often leads to a cleaner separation of concerns.
它提高了我们对于一个设计良好的、可维护的软件系统所需的、关注点分离的表达能力。
It enhances our ability to express the separation of concerns necessary for a well-designed, maintainable software system.
我们所指的关注点分离阶段是指使用不同的环境控制组成部署发布版本的代码流和其他文件。
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.
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.
业务集成得益于强制关注点分离集成数据和应用程序以满足业务要求。
Business integration benefits from an enforcement of separation of concerns to integrate data and applications as appropriate for business needs.
业务集成得益于强制关注点分离集成数据和应用程序以满足业务要求。
Business integration benefits from an enforcement of separation of concerns to integrate data and applications as appropriate for business needs.
应用推荐