pointcuts
美 
英
例句
As you can see, this sort of syntax error takes much longer to debug in the tools that don't have static checking of pointcuts.
由此可以看到，在没有切入点静态检查的工具中，这类语法错误需要更多时间调试。
If I modify my pointcuts to make them more accessible to mock targets, I also make them more accessible to non-test parts of the system.
如果修改切点以使它们更能被mock目标访问，也就使它们更可被系统中的非测试部分访问。
Writing good pointcuts is key to mastering AOP, although it is often a struggle for newcomers.
编写好的切入点是掌握好AOP的关键，尽管这对于新手来说通常不是一件容易的事。
The syntax for creating static crosscuts is quite different from that of dynamic crosscutting, in that there are no pointcuts or advices.
创建静态横切的语法和动态横切有很大的不同，即没有切入点和通知。
A more complete and fine-grained set of pointcuts allows more of the interesting points of program execution to be accessible to aspects.
更加完整和精细的切入点集合允许通过方面访问程序执行中更多有趣的点。
Figuring out what went wrong, especially when first coming up to speed on AOP and pointcuts, can be extremely time-consuming.
指出错误在哪特别费时，尤其在初次接触AOP和切入点时。
Aspects combine pointcuts and advice into a modular solution addressing a particular crosscutting concern.
切面是结合切入点和通知成一个模块方案，解决特殊的横切问题。
At the time of this writing, no AOP system supports annotation properties-based pointcuts.
在编写本文的时候，还没有支持基于注释属性的切入点的AOP系统。
Checking such pointcuts with a few representative mock targets is worthwhile.
用几个代表性的mock目标检查这种切点是值得的。
Only a few pointcuts are required for coarse-grained crosscutting and auxiliary aspects.
对于粗粒度的横切和辅助性方面，只需要很少的切入点。
Pointcut support for composition allows you to combine simple pointcuts into more complicated ones.
切入点支持复合（composition），这就允许把简单的切入点组合成更复杂的切入点。
Run time -- Interception and proxy-based mechanisms provide a means for matching pointcuts to determine when advice should be invoked.
运行时——拦截和基于代理的机制提供了切入点匹配的手段，可以决定什么时候应当调用通知。
Together, these two pointcuts define all of the join points with which we are concerned.
合起来，这两个切点定义了所有我们关注的连接点。
Note that at this time, AspectJ is the only tool that provides a static enforcement mechanism that employs pointcuts.
注意，目前AspectJ是惟一提供使用切入点的静态强制机制的工具。
We were able to do this easily because both pointcuts have an Employee parameter.
因为每个切点都有一个雇员参数，因此，我们可以很容易地完成这项工作。
The aspect encapsulates the join points, pointcuts, inter-type declarations, and advice for a crosscutting concern.
方面封装了一个横切关注点的连接点，切入点，类型间声明和参考建议。
Pointcuts allow you to unambiguously reference multiple join points in the program code (method content and processes).
衡切点允许您明确的引用程序代码（方法内容和过程）中的多个连接点。
When editing pointcuts, being forced to run the system and inspect the results to find affected join points is very time-consuming.
在编辑切入点时，不得不运行系统才能查看结果，寻找受影响的连接点是非常耗时的。
On the flipside, a broader set of pointcuts does have a pay-as-you-go property, as pointcuts can be learned as needed.
从反面来看，更广泛的切入点集合确实具备量入为出的属性，因为切入点可以边用边学。
Pointcuts can describe sets of join points by means of explicit enumeration.
切入点可以通过显式枚举方式描述连接点集合。
Join points, pointcuts, and advice address the dynamic properties of your software.
连接点，切入点和参考建议关注于你的软件的动态属性。
Together, pointcuts, advice, and inter-type declarations allow AOP languages to express crosscutting concerns explicitly.
切入点、通知和类型间声明组合在一起，使AOP语言可以清楚地表达横切问题。
Many aspects cannot be expressed without fine-grained pointcuts.
没有精细的切入点，许多方面就不能表达。
Join points are encapsulated in quantifiable expressions (queries) called "pointcuts. "
连接点被封装在被称作“pointcuts（横切点）”的可以计量的扩展（查询）之中。
Metadata brings additional information to selecting join points where Pointcuts use annotations to capture join points.
元数据给选择连接点（joinpoints）带来了附加信息，在那里Pointcuts使用注解来捕获连接点（joinpoints）。
You can take a more relaxed approach to describing pointcuts by using free-text description.
您可以采用一种更加宽松的方法来描述横切点，使用上下文无关的描述。
Trace defines three pointcuts; two of them are concrete and one abstract, as shown in Figure 2.
跟踪定义了三个切入点；其中的两个是具体的，一个是抽象的，正如图2所示。
Pointcuts are then used to define the join points at which advice in the aspect applies.
然后可以用切入点来定义将在其上应用方面中的通知的连接点。
These provide an elegant way of expressing pointcuts and advice in a single code module.
它提供一种在单个代码模块中表达切入点和通知的优雅的方式。
Pointcuts are just the first step in a design approach that minimizes entangling assumptions.
切入点仅仅是减少重重假设的设计方法的第一步。
The above method for describing pointcuts has proved useful, but at present there is no analogous method for describing process pointcuts.
上述用于描述横切点的方法已经被证明是有效的，但是目前并没有一种类似的方法可以用来描述过程横切点。
As a result, there is no import mechanism for pointcuts, and all type references must be fully qualified.
所以，没有切入点的import机制，所有的类型引用必须完全规范。
A mechanism for naming pointcuts facilitates readability and composition.
切入点的命名（naming）机制提高了可读性和复合性。
To fully support dynamic AOA weaving, RMC requires an embedded language for declaring process pointcuts.
为了完全支持动态AOA编排，RMC要求一种声明过程横切点的嵌入式语言。
Using pointcuts, you can easily define situations in which a timestamped object should have its stamp updated.
使用Pointcut，您可以方便地定义环境，加上时间戳记的对象将在其中更新戳记。
But it also means that little additional work for matching pointcuts needs to be done at run time.
但它也意味着在运行的时候，几乎不需要为了匹配切入点做额外的工作。
The learning curve for using new pointcuts is pay as you go.
使用新切入点的学习曲线是随用随学。
Concise aspect declarations and static checking for pointcuts.
简洁的方面声明和切入点的静态检查。
The pointcuts in these aspects look for the appropriate annotations.
这些方面中的切入点查找合适的标注。
Both pointcuts and their bindings to advice are declared in the aspects using XML annotations.
切入点和切入点到通知的绑定都在方面中用XML注释声明。
