Fetching strategy is a business level cross cutting concern and it changes based on the business use case.
抓取策略是个业务层的横切关注点，它会随着业务的变化而变化。
The ESB can implement or enforce cross-cutting aspects on behalf of service requesters and providers, removing such aspects from the concern of the requesters and providers.
ESB可以代表服务请求者和提供者实现或执行横切方面，从而从请求者和提供者的关注事项中消除此类方面。
So how do we implement a cross-cutting concern such as logging?
因此，怎样才能实现一个横切关注点，例如日志？
Avoided tying all code to particular instances of cross-cutting concern classes.
避免将所有代码与横切关注点类的特殊实例联系起来。
The type of logging required in our example is a cross-cutting concern.
在我们例子中所需的日志类型为横切关系。
A cross-cutting concern is a problem or issue that is Shared or exhibited across layers and subsystems. Examples of common concerns include.
横切关系是一个跨越各个层次或子系统进行分享和展示的问题。
The organizational structure in WebSphere Commerce is a cross-cutting concern, affecting many of the decisions made at design time for your site.
WebSphereCommerce中的组织结构非常值得关注，它影响设计站点时所做的许多决定。
The basic thumb rule toidentify a cross-cutting concern is: If a concern is repeated across classesspread over layers / tiers, then it is a cross-cutting concern.
识别一个横切关注点的经验法则是：如果一个关注点反复出现在不同类及层次中，那它是一个横切关注点。
In general, a cross-cutting concern is a concern that affects multiple components in a system.
一般来说，横切关注点是一个在系统中影响多个元件的关注点。
In general, a cross-cutting concern is a concern that affects multiple components in a system.
一般来说，横切关注点是一个在系统中影响多个元件的关注点。
应用推荐