The main concept is the join point.
主要概念就是连接点。
A join point is where the main program and the aspects meet.
连接点就是主程序和方面相遇的地方。
Base code is refactored to create a better join point model.
可以重构库代码创建更好的连接点模型。
This gives the benefit of static typing for join point context.
这为连接点上下文提供了静态类型化的好处。
There are two ways to approach configuring tests at a join point.
在一个连接点上配置测试有两种方法。
For instance, the method bar in object Foo could be a join point.
例如，对象Foo中的方法bar就可以是一个连接点。
A join point is an identifiable point in the execution of a system.
连接点是系统执行中的一个可标识的点。
Advice is code that executes before, after, or around a join point.
Advice是在join point之前、之后或周围执行的代码。
To understand pointcuts, you'll need to know what a join point is.
要理解Pointcut，必需知道join point是什么。
Join point is an abstract notion; one does not actively define a join point.
连接点是个抽象的概念；不用主动定义一个连接点。
AspectJ offers both reflective access and the traditional join point context.
AspectJ提供了反射访问和传统的连接点上下文。
Provides a join point for multiple input messages that enables message aggregation.
提供多个输入消息的联接点，该联接点支持消息聚合。
Simple join point model is well suited to coarse-grained aspects and easier to learn.
简单的连接点模型很适于粗粒度的方面，更容易学习。
A join point is a point in the execution of a program where you can usefully join behavior.
连接点是程序执行中可以有效连接行为的点。
Tool support answers these questions by indicating when a join point is affected by advice.
通过指出什么时候连接点受通知影响，AOP工具回答了这些问题。
And if you invoke the IClosure object after the join point completes, results may vary.
如果在连接点完成之后调用IClosure对象，那么结果可能有所不同。
They should describe what is true at the join point - not what should happen at those points.
注解应该描述清楚连接点上什么是符合要求的，而不是在这些点上应该发生什么。
The content assist pop-up shows all the join point context available within the advice body.
内容辅助弹出对话框则显示了通知体中所有可以使用的连接点上下文。
Both the annotation and the newly created instance are captured as context at the join point.
标注和新创建的实例，都在连接点上作为上下文被捕捉到。
A join point is a precise point of execution in a program, such as a method found in a class.
一个连接点(join point)是程序执行中一个精确执行点，比如类中的一个方法。
This yields a performance boost since join point context doesn't need to be accessed reflectively.
这会带来性能飞跃，因为不需要以反射的形式访问连接点上下文了。
Spring AOP takes a different approach and purposely limits the expressiveness of its join point model.
SpringAOP采用了不同的技术，目的是限制它的连接点模型的表现力。
They execute before the join point, after the join point, and instead of the join point, respectively.
他们分别在连接点之前，之后，或是取代连接点而执行。
Another problem is that the crosscutting views only show matches based on static join point shadows.
另一个问题是横切视图只显示了基于静态联结点shadow的匹配。
In these cases you can query the object representing the advised join point for its associated annotations.
在这种情况下，可以查询表示已通知连接点的对象来获得相关的注释。
It is as general as a join point, safer than advice (because the context is more hidden), and as reusable as Command.
它和连接点一样通用，比通知更安全(因为上下文更加隐蔽)，并且和Command一样可以重用。
Next, I'll quickly review the basics of AOP's join point model and explain where it would benefit from metadata fortification.
下一步，我将快速地回顾AOP的连接点模型的基本内容，并说明它从元数据增强中可以获得哪些好处。
Precondition tests are handled by before advice, which is executed just before the corresponding method execution join point.
前置条件测试由before建议处理，该建议就在对应的方法执行连接点之前执行。
The second statement identifies the exact join point where the advice is executed and makes use of the AspectJ JoinPoint class.
第二条语句指明了通知被执行的确切连接点，并且应用了AspectJ的joinpoint类。
At the heart of each of the AOP tools is a join point model, which provides a means of identifying where the crosscutting is happening.
位于每个AOP工具核心的是连接点模型，它提供了一种机制，可以识别出在哪里发生了横切。
应用推荐