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.
由此可以看到，在沒有切入點靜態(tài)檢查的工具中，這類語法錯誤需要更多時間調試。
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目標訪問，也就使它們更可被系統(tǒng)中的非測試部分訪問。
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.
創(chuàng)建靜態(tài)橫切的語法和動態(tài)橫切有很大的不同，即沒有切入點和通知。
A more complete and fine-grained set of pointcuts allows more of the interesting points of program execution to be accessible to aspects.
更加完整和精細的切入點集合允許通過方面訪問程序執(zhí)行中更多有趣的點。
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系統(tǒng)。
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是惟一提供使用切入點的靜態(tài)強制機制的工具。
We were able to do this easily because both pointcuts have an Employee parameter.
因為每個切點都有一個雇員參數(shù)，因此，我們可以很容易地完成這項工作。
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.
在編輯切入點時，不得不運行系統(tǒng)才能查看結果，尋找受影響的連接點是非常耗時的。
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.
連接點，切入點和參考建議關注于你的軟件的動態(tài)屬性。
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.
元數(shù)據給選擇連接點（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.
它提供一種在單個代碼模塊中表達切入點和通知的優(yōu)雅的方式。
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機制，所有的類型引用必須完全規(guī)范。
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.
為了完全支持動態(tài)AOA編排，RMC要求一種聲明過程橫切點的嵌入式語言。
Using pointcuts, you can easily define situations in which a timestamped object should have its stamp updated.
使用Pointcut，您可以方便地定義環(huán)境，加上時間戳記的對象將在其中更新戳記。
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.
簡潔的方面聲明和切入點的靜態(tài)檢查。
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注釋聲明。
