All are examples of what are called crosscutting concerns.
所有这些都是所谓横切关注点的例子。
Are they also appropriate for dealing with crosscutting concerns?
那么它们是否也适用于横切关注点呢？
AOP is key to managing crosscutting concerns in application development.
AOP是在应用程序开发中管理横切关注点的关键。
In fact, the injection of code for crosscutting concerns is a pattern of sorts.
实际上，横切关注点代码的注入，就是一种类型的模式。
A key concept to grasp is that crosscutting concerns divide into two different areas.
一个要掌握的关键概念是横切关注点分为两个区域。
By compartmentalizing aspect code, crosscutting concerns become easy to deal with.
通过划分Aspect代码，横切关系变得容易处理。
Annotations are an easy way to capture certain crosscutting concerns in the applications.
用注解捕获应用中特定的横切关注点是一种很简单的方式。
AOP modularizes crosscutting concerns, so I should look for crosscutting concerns in my code.
AOP模块化了横切关注点，因此我要在代码中寻找横切关注点。
However, it will help you to understand and gain confidence in your application's crosscutting concerns.
不过，它可帮助您理解并获得对应用程序的横切关注点的信任。
AOP modularizes crosscutting concerns, so I should look for code that is scattered and tangled in my code.
AOP模块化横切关注点。因此应该寻找那些分散和纠缠在代码中的代码。
It realizes the decoupling of the core concerns and the crosscutting concerns from function and data.
该架构从功能和数据两方面实现了核心关注点和横切关注点彻底解耦。
Signature-based pointcuts cannot capture the join points needed to implement certain crosscutting concerns.
基于签名的切入点不能捕获实现某种横切功能所需要的连接点。
AOP tools are designed to modularize crosscutting concerns, such as authentication and transaction management.
AOP工具的设计目标是把横切的问题(例如认证和事务管理)模块化。
As a result, crosscutting concerns like logging, transactions, and security no longer intrude on your application code.
因此，横切关注点(如日志、事务和安全)不会再干扰应用程序代码。
Typical crosscutting concerns include logging, context-sensitive error handling, performance optimization, and design patterns.
典型横切关系包括日志记录、对上下文敏感的错误处理、性能优化以及设计模式。
Hyperspaces goes beyond the encapsulation of crosscutting concerns and attempts to manage multi-dimensional separation of concerns.
Hyperspaces超越了对横切关系的封装，并尝试管理关系的多维分离。
In addition to untangling element signatures, annotations can be used to express any data associated with your code's crosscutting concerns.
除了排除元素签名的纠结外，还可以使用注释来表达与代码的横切关注相关的任何数据。
Since crosscutting concerns are so fundamental in systems, MDD tools will benefit from modeling crosscutting structure and generating aspects.
由于横切的问题在系统中是如此基本的一个问题，所以MDD工具会从模型化的横切结构以及生成的方面中获益。
Ensuring that crosscutting concerns do not obscure mainline business logic-a real danger as different concerns add up as development progresses.
确保横切关注点不混淆主要的业务逻辑——随着开发的进展，这很有可能成为危险之处。
A novel method to discover crosscutting concerns from source-code for transformation from legacy system to Aspect-oriented system was proposed.
为了将传统方法开发的系统转换成面向方面的系统，实现关注分离，提出了一种从遗产系统中发现横切关注点的方法。
If you implement your crosscutting behavior with aspects, however, you gain new ways to test (and understand) your application's crosscutting concerns.
不过，如果用方面实现横切行为，那么就有了测试(并理解)应用程序的横切关注点的新方法。
Using aspect oriented programming the crosscutting concerns and core function concerns can be designed and developed concurrently and independently.
运用面向方面的编程技术可实现中间件横切关注和核心功能关注的并行设计与开发。
The difference is that you now map the system's crosscutting concerns to aspects that use a multidimensional interface, which is projected into the associated dimensions.
区别是现在将系统的横切关注点映射到使用了投射到相关维中的多维接口的方面。
With the popularization of AOP, it has become both possible and desirable to write tests that check crosscutting concerns independent of their realization in a target system.
随着AOP的普及，编写与横切关注点在目标系统中的实现无关的、对其进行检查的测试已变得可行并且值得去做。
The purview control of the log record and the management of the users are used as the example to study the crosscutting concerns, and the relevant solutions are proposed.
实例研究表明，该方法在并发软件设计阶段实现了横切关注点的分离策略，并使得系统模型具有松耦合、适应性和可跟踪性的优点。
Considering metadata as an aspectual interface from classes to crosscutting concerns in the system translates some of the best practices from the object-oriented world to AOP.
将元数据考虑为类中的一个方面化接口，通过这种方法来横切系统中的一些关注点，这样，可以将面向对象世界中的一些最佳实践应用到AOP中。
If you modularize crosscutting concerns, such as logging and transaction management, it becomes possible to add new features to your code without modifying each class individually.
如果对横切关注点(例如日志和事务管理)进行了模块化，那么不用修改每个单独的类，就可以向代码中添加新特性。
You can leverage this separation of concerns to test their behavior separately from the crosscutting specification.
可以利用这种关注点的分离分别测试横切规范及它们的行为。
Treat global concerns globally: Program elements should not have much say in the participation of concerns such as tracing and profiling in a crosscutting implementation.
要全局地对待全局关注点：程序元素不应当对关注点(比如在横切实现中进行跟踪和分析)的参与起什么作用。
The real beauty of treating safety concerns in a crosscutting manner, however, is that you can effectively reuse them.
以横切的方式对待安全性关注点的真正妙处是：可以有效地重用这些关注点。
应用推荐