Top
首页 > 老文章 > 正文

AOP introduced a new way to do wishful thinking

AOP introduced a new way to do wishful thinking

AOP introduced a new way to do wishful thinking
发布时间:2006-03-08 22:25        来源:        作者:

http://spaces.msn.com/members/nctaowen/

The essence of AOP is the idea: when x, do y. It gives you the power to insert any code at any place. It might change the way you think given the ability to introduce new things after you written them. Actually, I do think it will change the way to design, as you can do wishful thinking but not relying on additional parameters (these parameters may be somewhat higher-order function in functional programming or other object instance in object-oriented programming). With AOP, you can write down methods of class but not implement them. By weaving aspects later, the behavior can be fully implemented. This is different from traditional ways, in the past, you have to specifiy which one to call or use at the point you want to call or use them.  By using AOP, you can define a method local to the object, and leave it blank. You give it some meanings, which may be a comlex collaboration between serval objects. But whatever the meaning is (or say pre-defined contracts), the method is still blank. You call it when you want to take the action which is binded to it in mind. Then, after you finished the work of designing the class, you can define a aspect to weave the behavior to the blank method. Now, you see AOP gives you a new power to use something before it is implemented, hence allows you to do wishful thinking which is the key to think and design complex computer programs.

 

I wrote a sample project which only doese trivial printing. You can download it at

http://www.cnblogs.com/Files/taowen/experiment.zip

public class ClassA {
 
 public void doSomething() {
  System.out.println("going to do something");
  takeAction();
  System.out.println("have done something");
 }
 
 @TakeAction
 private void takeAction() {
  
 }

}

when writing ClassA you don not care with who and how to take the action.

 

public aspect ABCollaboration {
 
 ClassB b = new ClassB();
 
 void around() : (call (@TakeAction * * (..))) {
  b.doSomething();
 }
 
 public static void main(String[] args) {
  new ClassA().doSomething();
 }

}

 

By using a aspect, you weave the behavior later.

加载更多

专题访谈

合作站点
stat