This is called defining join points in AspectJ.
这被称作在AspectJ中定义连接点。
Join points represent well-defined points in a program's execution.
joinpoint表示在程序执行中明确定义的点。
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.
切入点选择连接点，并收集所选的连接点处的上下文。
If you want the aspect to affect many join points, pick a few representative examples.
如果方面会影响多个联结点，那么就选择几个代表例子。
Dynamic join points are where aspect execution meets the execution of the program.
动态连接点是方面执行与程序执行相遇的地方。
Conversely, when you write an aspect, you immediately see what join points it affects.
反过来，在编写方面的时候，可以立即看到这个方面影响了哪个连接点。
Join points are encapsulated in quantifiable expressions (queries) called "pointcuts."
连接点被封装在被称作“pointcuts(横切点)”的可以计量的扩展(查询)之中。
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.
方法执行连接点，与方法返回之前的生命周期对应。
Situations like this one invite the use of metadata to capture the required join points.
像这样的情况就要用元数据捕获所需要的连接点。
Pointcuts are then used to define the join points at which advice in the aspect applies.
然后可以用切入点来定义将在其上应用方面中的通知的连接点。
Excluded : this matches all join points within the FFDC aspect and any of its sub aspects.
excluded：它和FFDC方面和其子方面中的所有join points匹配。
For an AOP approach to be advantageous, multiple join points for a single concern must exist.
对于一个有利的AOP方法来说，用于单独一个关注的多个连接点必须存在。
Type isn't the only consideration when selecting join points: properties may also be considered.
在选择连接点时，类型不是惟一要考虑的事项：还可以考虑属性。
Verify manually that the list is complete and does not include join points that should be omitted.
人工验证清单是否完整，并且不包含应忽略的联结点。
In such cases, the annotator-supplier design avoids the risk of missed annotations for join points.
在这种情况下，有一种注释者-供应者设计避免了错过连接点的注释的风险。
You use a pointcut to specify join points of a program, and advice to specify the behavior to join.
可以使用切入点指定程序的连接点，用通知（advice）指定连接的行为。
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.
基于签名的切入点不能捕获实现某种横切功能所需要的连接点。
At run time, Contract4J USES built-in aspects to advise the join points where the tests should be executed.
在运行时，Contract4J使用内置的方面建议应该在其中执行测试的连接点。
Containment — Join points that correspond to places in the code contained within certain classes or methods.
包含(Containment)——与包含在某个类或方法中的代码位置对应的连接点。
One of the hard things about testing a widespread crosscutting concern is that it can advise so many join points.
关于测试广泛分布的横切关注点的一个难题是它会报告太多的联结点。
In the above example, the lockManagedExecution() pointcut selects a subset of join points that need lock management.
在上面的例子中，lockManagedExecution()切入点选择了需要用锁管理的连接点子集。
At the core of each approach, however, is the mechanism for accessing, composing, naming, and abstracting join points.
但是，每种技术的核心，都是连接点的访问、编辑、命名和抽象机制。
While enumeration can be useful, it is often more convenient to express join points by means of structural properties.
虽然枚举可能很有用，但是用结构化属性的方式表示连接点通常更方便。
Pointcuts allow you to unambiguously reference multiple join points in the program code (method content and processes).
衡切点允许您明确的引用程序代码(方法内容和过程)中的多个连接点。
The key is to write a test that will fail if the aspect misbehaves or does not apply to the join points you intend it to.
关键是编写一个当方面行为错误或者没有应用到希望它应用的联结点处时会失败的测试。
Typical join points in AspectJ include method calls, access to class members, and the execution of exception handler blocks.
AspectJ中典型的joinpoint包括方法调用、对类成员的访问以及异常处理程序块的执行。
应用推荐