连接点就是主程序和方面相遇的地方。
A join point is where the main program and the aspects meet.
连接点是程序执行中可以有效连接行为的点。
A join point is a point in the execution of a program where you can usefully join behavior.
在一个连接点上配置测试有两种方法。
There are two ways to approach configuring tests at a join point.
像这样的情况就要用元数据捕获所需要的连接点。
Situations like this one invite the use of metadata to capture the required join points.
通知是可以被切面应用到连接点的行为。
Advice is behavior that can be applied by aspects to joinpoints.
可以重构库代码创建更好的连接点模型。
Base code is refactored to create a better join point model.
连接点是系统执行中的一个可标识的点。
A join point is an identifiable point in the execution of a system.
静态连接点允许方面定义类上的新成员。
Static join points allow aspects to define new members on a class.
这个缓存区域帮助减少串行化和多个连接点的开销。
This cache region helps to alleviate overhead with serialization and multiple connection points.
这被称作在AspectJ中定义连接点。
这为连接点上下文提供了静态类型化的好处。
This gives the benefit of static typing for join point context.
典型的，对每一个关注点存在着许多连接点。
主要概念就是连接点。
动态连接点是方面执行与程序执行相遇的地方。
Dynamic join points are where aspect execution meets the execution of the program.
切入点可以通过显式枚举方式描述连接点集合。
Pointcuts can describe sets of join points by means of explicit enumeration.
此处“大脑”一词指由许多连接点组成的意识。
The "brain" here refers to a consciousness made up of connected points.
例如，如何捕获需要事务管理或者授权的连接点呢？
For example, how would you capture join points requiring transaction management or authorization?
连接点是个抽象的概念；不用主动定义一个连接点。
Join point is an abstract notion; one does not actively define a join point.
方法执行连接点，与方法返回之前的生命周期对应。
Method execution join points correspond to the life cycle of a method until it returns.
您需要一个本地的中央连接点，它能够支持以上几种连接类型。
You need a local, central connection point that supports the above connection types.
他们不想仅作为伊斯坦布尔和欧洲之间的一个连接点。
They want to be more than just a link in the chain between Istanbul and Europe.
简单的连接点模型很适于粗粒度的方面，更容易学习。
Simple join point model is well suited to coarse-grained aspects and easier to learn.
他们分别在连接点之前，之后，或是取代连接点而执行。
They execute before the join point, after the join point, and instead of the join point, respectively.
切入点选择连接点，并收集所选的连接点处的上下文。
Pointcuts select join points and collect the context at selected join points.
这会带来性能飞跃，因为不需要以反射的形式访问连接点上下文了。
This yields a performance boost since join point context doesn't need to be accessed reflectively.
标注和新创建的实例，都在连接点上作为上下文被捕捉到。
Both the annotation and the newly created instance are captured as context at the join point.
在这种情况下，可以查询表示已通知连接点的对象来获得相关的注释。
In these cases you can query the object representing the advised join point for its associated annotations.
但是，每种技术的核心，都是连接点的访问、编辑、命名和抽象机制。
At the core of each approach, however, is the mechanism for accessing, composing, naming, and abstracting join points.
当你选择一系列连接点的时候，你可以为它们提供参考建议。
When you select a set of join points, you provide advice for them.
使用AOP，我们需要一个在一个程序中识别连接点的方法。
With AOP, we need a way to identify join points in a program.
应用推荐