pointcut

A similar functionality could be helpful for pointcut debugging purposes .

一个类似的功能有助于横切点调试用途。

A " pointcut " is a construct used to programmatically declare and group join points .

一个“衡切点”是一个被用作程序声明和分组连接点的构造。

The method name is used as the name of the pointcut .

方法名被用作切入点的名称。

Given that we needed a pointcut expression language , the choice was simple .

如果我们需要一种切入点表达语言，那么选择就会很简单。

A pointcut specifies the properties of a given element of a program .

切入点指定程序给定元素的属性。

First , the aspect isn 't reusable because the pointcut definition is system specific .

首先，这个方面不是可重用的，因为切入点定义是特定于系统的。

That pointcut definition will only be known after the application starts getting defined .

这个横切定义只有在应用程序开始定义之后才会得知。

Future versions of AOP systems will support this sort of pointcut .

下一版本的AOP系统支持这种切入点。

As with the Customer class , adding a step would simplify the pointcut .

与Customer类一样，增加这一步会简化这个切入点。

Note that we can use keywords for aspect and pointcut .

请注意我们可以使用aspect和pointcut关键词。

Let 's add a pointcut to match methods returning int

让我们添加一种切入点来匹配返回int的方法

A pointcut is in essence a construct to capture join points .

一个切入点（pointcut）本质上一个用于捕捉连接点的结构。

This combines the pointcut with the advice method , making the aspect a complete module .

这将切入点和通知方法结合在一起，使切面成为一个完整的模块。

Different variations of that theme can be used where appropriate without having to write complex pointcut code .

可以在适当的地方使用不同的主题变量，不必编写复杂的切入点代码。

In practice , however , you would likely use wildcards to simplify the pointcut definition .

不过在现实中，可能会使用通配符简化切入点的定义。

The pointcut expression is the key .

切入点表达式是关键。

One of AspectJ 's primary goals is to offer them for pointcut expressions .

AspectJ的主要目标就是把它们提供给切入点表达式。

Benefiting from type safety , where types in the method signature are specified in the pointcut .

从类型安全中受益，其中方法签名中的类型是在切入点中指定。

Lets look at pointcut reuse in practice .

让我们看一下实际中切入点的重用。

AspectJ has a well thought out , rigorously defined and well documented pointcut language .

AspectJ有个思路很好，严格定义和充足文档的切入点语言。

The sophistication of the pointcut language is a differentiating factor among the various AOP systems .

切入点语言的复杂程度是不同AOP系统的一种区分元素。

A sub-aspect needs to provide this information , in the form of a pointcut .

一个子方面需要提供这种信息，也就是pointcut的形式。

An advice is executable code for a pointcut .

通知（advice）是切入点的可执行代码。

The power of the AspectJ pointcut expression language is not merely about allowing sophisticated constructs .

AspectJ切入点表达式语言的强大不仅仅是关于复杂的结构。

AspectJ pointcut expression language support , allowing developers to apply cross-cutting security logic across their Spring managed objects

AspectJ切入点表达式语言支持，允许开发者在Spring管理的对象上应用横切（cross-cutting）安全逻辑

A pointcut is a matching rule .

切入点是匹配规则。

The subaspect below defines a pointcut that captures the join points needing transaction management support .

下面的子方面定义了一个捕获需要事务管理支持的连接点的切入点。

Judiciously using wildcards in join point signatures often leads to good , succinct pointcut definitions .

在连接点签名中明智地使用通配符通常可以产生好的、简洁的连接点定义。

The decision usually comes down to whether it makes sense to externalize the pointcut expression from Java code altogether .

决定通常取决于使切入点描述完全从Java代码具体出来是否有意义。

Pointcut syntax differs in the various metadata-fortified AOP systems .

切入点语法在不同的元数据增强的AOP系统中是不同的。