Join points may contain other join points.
joinpoint可以包含其它join point。
This is called defining join points in AspectJ.
这被称作在AspectJ中定义连接点。
A pointcut is in essence a construct to capture join points.
一个切入点(pointcut)本质上一个用于捕捉连接点的结构。
With AOP, we need a way to identify join points in a program.
使用AOP，我们需要一个在一个程序中识别连接点的方法。
Static join points allow aspects to define new members on a class.
静态连接点允许方面定义类上的新成员。
Pointcuts can describe sets of join points by means of explicit enumeration.
切入点可以通过显式枚举方式描述连接点集合。
Pointcuts select join points and collect the context at selected join points.
切入点选择连接点，并收集所选的连接点处的上下文。
Dynamic join points are where aspect execution meets the execution of the program.
动态连接点是方面执行与程序执行相遇的地方。
Situations like this one invite the use of metadata to capture the required join points.
像这样的情况就要用元数据捕获所需要的连接点。
This is a useful option when there is a clear way to express participating join points.
在有明确的方法表示特定的连接点时，这是一种有用的选择。
Method execution join points correspond to the life cycle of a method until it returns.
方法执行连接点，与方法返回之前的生命周期对应。
Pointcuts are then used to define the join points at which advice in the aspect applies.
然后可以用切入点来定义将在其上应用方面中的通知的连接点。
Type isn't the only consideration when selecting join points: properties may also be considered.
在选择连接点时，类型不是惟一要考虑的事项：还可以考虑属性。
For example, how would you capture join points requiring transaction management or authorization?
例如，如何捕获需要事务管理或者授权的连接点呢？
You use a pointcut to specify join points of a program, and advice to specify the behavior to join.
可以使用切入点指定程序的连接点，用通知（advice）指定连接的行为。
In such cases, the annotator-supplier design avoids the risk of missed annotations for join points.
在这种情况下，有一种注释者-供应者设计避免了错过连接点的注释的风险。
Verify manually that the list is complete and does not include join points that should be omitted.
人工验证清单是否完整，并且不包含应忽略的联结点。
Some primitive pointcuts match only join points of a specific kind (for example, method executions).
有些原生切入点只与特定类型的连接点匹配（例如，方法执行）。
For example, an aspect related to persistence might need access to an object's initialization join points.
例如，与持久性有关的方面可能需要访问对象的初始化连接点。
Signature-based pointcuts cannot capture the join points needed to implement certain crosscutting concerns.
基于签名的切入点不能捕获实现某种横切功能所需要的连接点。
While enumeration can be useful, it is often more convenient to express join points by means of structural properties.
虽然枚举可能很有用，但是用结构化属性的方式表示连接点通常更方便。
In the above example, the lockManagedExecution() pointcut selects a subset of join points that need lock management.
在上面的例子中，lockManagedExecution()切入点选择了需要用锁管理的连接点子集。
The sequence diagram in Figure 1 highlights a few of the dynamic join points that result from operations on an Account.
图1中的顺序图突出了在 Account操作上形成的一些动态连接点。
Typical join points in AspectJ include method calls, access to class members, and the execution of exception handler blocks.
AspectJ中典型的joinpoint包括方法调用、对类成员的访问以及异常处理程序块的执行。
One of the best practices of getting most out of AOP is to use to metadata to capture join points for cross-cutting concerns.
从AOP获得大部分好处的最佳实践之一就是使用元数据去为横向关注点（cross-cuttingconcerns）捕获连接点（join points）。
Compare the maps in the crosscutting comparison tool to detect any unwanted changes to the join points affected by your aspects.
在横切比较工具中比较这些图，以发现受方面影响的联结点所出现的不希望的改变。
An AOP system that supports consuming annotations will let you select join points based on annotations associated with program elements.
支持消费注释的AOP系统使您可以基于与程序元素相关联的注释选择连接点。
For crosscutting functionality that could not capture the needed join points in a generic manner, however, this approach would be limiting.
可是对于不能用一般方法捕获所需连接点的横切功能，这种方法存在局限性。
As shown in Figure 2, a rule flow may contain branch points and join points, which allows for very sophisticated management of rule execution.
如图2所示，规则流可包含支点和接点，允许极为细致地管理规则执行。
All other affected join points show the same structure (for example, types affected by inter-type declarations and call sites affected by advice).
所有其他受影响的连接点都显示了相同的结构(例如，受类型间声明影响的类型，以及受通知影响的调用站点。)
应用推荐