Spring AOP takes a different approach and purposely limits the expressiveness of its join point model.
SpringAOP采用了不同的技术，目的是限制它的连接点模型的表现力。
Next, I'll quickly review the basics of AOP's join point model and explain where it would benefit from metadata fortification.
下一步，我将快速地回顾AOP的连接点模型的基本内容，并说明它从元数据增强中可以获得哪些好处。
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工具核心的是连接点模型，它提供了一种机制，可以识别出在哪里发生了横切。
The expressiveness of an AOP tool's join point model determines the granularity of the join points available, and how those join points are matched.
一个AOP工具连接点模型的表达方式决定了可用的连接点粒度，以及连接点如何匹配。
In the next section I'll quickly review the basics of AOP's join point model, then explain where it could be beneficially fortified with metadata.
在下一节中，我将快速地回顾AOP的连接点模型(join point model)的基本内容，然后说明是如何用元数据增强它。
Each of the AOP tools reviewed in this article employs a join point model and mechanisms for explicitly declaring a program's crosscutting structure.
本文介绍的每个AOP工具都采用了连接点(join point)模型和机制，显式地声明程序的横切结构。
The join point model, the most fundamental and distinguishing concept in AOP, defines which join points in a system are exposed and how they are captured.
连接点模型是AOP中最基本和最独特的概念，它定义了系统中哪个连接点是公开的，以及如何捕获它们。
While the tools have converged on the idea of a join point model, pointcuts, advice, and inter-type declarations, there are significant trade-offs inherent in each tool's handling of AOP syntax.
虽然这些工具已经集中在连接点模型、切入点、通知和类型间声明的思想上，但是每种工具在处理AOP语法时，仍有各自明显的优缺点。
While the tools have converged on the idea of a join point model, pointcuts, advice, and inter-type declarations, there are significant trade-offs inherent in each tool's handling of AOP syntax.
虽然这些工具已经集中在连接点模型、切入点、通知和类型间声明的思想上，但是每种工具在处理AOP语法时，仍有各自明显的优缺点。
应用推荐