subaspect

subaspect

美 　英

• 網絡分體

例句

In this iteration I'm going to modify each method to have an annotation and go back to one subaspect for the system (as in Version 2).

在這個回合中，我準備修改每一個方法，讓它有一個注釋，并退回到只在系統中使用一個子方面（像在版本2中一樣）。

Instead of a large N, I've reduced the system coupling to a smaller number of program elements captured by each subaspect, say n-to-1.

我已經將系統耦合減少到每個子方面所捕獲的更少的程序元素數（比如說從n減少到1），以此取代了那個大大的N。

They rely on a pointcut rather than a type, either assuming nothing or deferring a context specification to a concrete subaspect.

依賴于切入點而不是類型，要么不作任何假定，要么將上下文規格推遲到具體的子方面中。

While it's an improvement, this design still leaves us with an N-to-1 dependency between the subaspect and classes.

雖然有了改進，但是這種設計仍然是一個子方面與類之間的N對一依賴關系。

However, separating the base aspect from the metadata-driven subaspect has a few advantages.

不過，將基本方面與元數據驅動的子方面分離具有若干好處。

Listing 5 shows a metadata-drive subaspect of the ReadWriteLockSynchronizationAspect aspect for a banking system.

清單5顯示了銀行系統的ReadWriteLockSynchronizationAspect方面的、元數據驅動的子方面。

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

下面的子方面定義了一個捕獲需要事務管理支持的連接點的切入點。

Class with a participant subaspect that is responsible for defining the pointcut for the embedded class.

類，它負責定義嵌入類的切入點。

The subaspect itself will be reusable across systems.

這個子方面本身可以在系統中重用。

Now if a class changes, I need to modify only the nested subaspect in that class.

現在，如果類發生改變，那么只需要修改類中嵌套的子方面即可。

Listing 3 shows a banking-specific subaspect that extends the TxMgmt aspect in Listing 2.

清單3顯示了一個特定于銀行的子方面，它擴展了清單2中的TxMgmt方面。

Next, I need to write a subaspect for my base aspect.

下一步，需要為這個基本方面編寫一個子方面。