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.

下一步，需要为这个基本方面编写一个子方面。