Note that we can use keywords for aspect and pointcut.
请注意我们可以使用aspect和pointcut关键词。
Later in the article, I rewrite the pointcut as I demonstrate some of the testing patterns.
在本文的后面，我将重写这个切点以展示一些测试模式。
The pointcut in the example uses a modifier and wildcard pattern to express "all public methods."
示例中的切入点使用了修饰符（modifier）和通配符（wildcard）模式来表达“所有公共方法”。
You use a pointcut to specify join points of a program, and advice to specify the behavior to join.
可以使用切入点指定程序的连接点，用通知（advice）指定连接的行为。
The Listing 3 version of the code shows how I can access the actual method information from the pointcut.
清单3中的代码展示了如何访问pointcut中的实际方法信息。
In a future version of AJDT, a "USES pointcut" relationship could be exposed to facilitate this connection.
在AJDT的未来版本中，可能会公开“使用切入点(usespointcut)”来帮助实现这个连接。
The pointcut expression language is the same as in AspectJ's own syntax, and the semantics are identical.
这种切入点表达语言和AspectJ自己的语法一样，而且语义相同。
With 2.6.0 we added refactoring support for the p-namespace and for renaming advice and pointcut definitions.
在2.6.0中，我们为p命名空间增加了重构支持，还增加了advice和pointcut定义的重命名支持。
The pointcut required in these situations can get unwieldy, as you can see for yourself in the following example.
在这种情况下，所需要的切入点可能会变得很难处理，从下面的例子中就可看到。
While declaring void limits the reach of the testCase() pointcut, it reduces complexity and increases protection.
虽然声明void限制了testCase()切入点的应用范围，但是这样降低了复杂性，增强了安全性。
In the above example, the lockManagedExecution() pointcut selects a subset of join points that need lock management.
在上面的例子中，lockManagedExecution()切入点选择了需要用锁管理的连接点子集。
If you develop with aspects, however, you could represent such behavior as advice, applied to any operation that matches a certain pointcut.
但是如果用方面开发，那么就可以将这些行为表示为建议(advice)，应用到所有匹配某个切点(pointcut)的操作。
It's called when the pointcut is supposed to be executed and has the flexibility to decide when — and even if — the pointcut actually does execute.
当要执行pointcut时调用它，并且具有决定什么时候执行——甚至是否执行——pointcut的灵活性。
The @Pointcut annotation allows us to define pointcut expressions and, where necessary, the number and type of arguments to be bound by the pointcut.
@Pointcut注解允许我们定义切入点表达式，而且必要时，还有被切入点绑定的参数的个数和类型。
Instead of using one subaspect for my whole system, I can use many subaspects -- one per subsystem -- making it possible to write a relatively stable pointcut.
不是在整个系统中使用一个子方面，而是使用许多子方面 ——每个子系统一个子方面，这使得编写相对稳定的切入点成为可能。
A pointcut is basically just a place to interrupt the "normal" (as defined by the source code) flow of your application's execution and do something different.
pointcut基本上只是一个中断应用程序执行的(由源代码定义的)“正常”流程并做一些不同的事情的地方。
The trick is to understand that if you cannot define a signature for the whole system, you need to break it up into smaller subsystems and define a pointcut for each one.
当不能为整个系统定义一个签名时，要知道将它分解成小的子系统，并为每个子系统定义切入点。
For example, you could use an execution(* *.get*()) || execution(boolean *.is*()) pointcut to capture execution of all getter methods and execution(void *.set*(*)) for all setters.
例如，可以使用一个execution(* *.get*()) || execution(boolean *.is*())切入点捕获所有getter方法的执行，对所有setter 使用 execution(void *.set*(*))。
The second pointcut, employeeFinanceUpdates, describes all join points where there is a call to any method that begins with update, ends with Info, and has one argument of type Employee.
第二个切点，employeeFinanceUpdates,描述了所有以update开头， 以Info, 结尾的，具有一个Employee类型实参的方法的调用点。
Pointcut as a design abstraction.
作为设计抽象的切入点。
Pointcut composition can also be done in Spring AOP XML.
切入点组合同样可以在SpringAOPXML中完成。
Pointcut composition can also be done in Spring AOP XML.
切入点组合同样可以在SpringAOPXML中完成。
应用推荐