学习笔记：AOP(before、after)

代码(转bea)
applicationContext.xml

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd">

<beans>
<!--    mypack.MethodTracing-->
<!-- Bean configuration -->
<bean id="businesslogicbean"
class="org.springframework.aop.framework.ProxyFactoryBean">
<property name="proxyInterfaces">
<value>mypack.IBusinessLogic</value>
</property>
<property name="target">
<ref local="beanTarget" />
</property>
<property name="interceptorNames">
<list>
<value>theTracingBeforeAdvisor</value>
<value>theTracingAfterAdvisor</value>
</list>
</property>
</bean>
<!-- Bean Classes -->
<bean id="beanTarget" class="mypack.BusinessLogic" />

<!-- Advisor pointcut definition for before advice -->
<bean id="theTracingBeforeAdvisor"
class="org.springframework.aop.support.RegexpMethodPointcutAdvisor">
<property name="advice">
<ref local="theTracingBeforeAdvice" />
</property>
<property name="pattern">
<value>.*</value>
</property>
</bean>

<!-- <value>.*</value>：该表达式选择advisor所关联到的一个或多个bean上的所有联结点。 -->
<!-- <value>./IBusinessLogic/.foo</value>：该表达式只选择IbusinessLogic接口上的foo()方法的联结点。-->
<!-- 如果是advisor所关联到的bean，则该表达式只选择IBusinessLogic接口上的联结点。 -->

<!-- Advisor pointcut definition for after advice -->
<bean id="theTracingAfterAdvisor"
class="org.springframework.aop.support.RegexpMethodPointcutAdvisor">
<property name="advice">
<ref local="theTracingAfterAdvice" />
</property>
<property name="pattern">
<value>.*</value>
</property>
</bean>

<!-- Advice classes -->
<bean id="theTracingBeforeAdvice" class="mypack.MethodTracing.TracingBeforeAdvice" />
<bean id="theTracingAfterAdvice" class="mypack.MethodTracing.TracingAfterAdvice" />

</beans>

IBusinessLogic

public interface IBusinessLogic {
	public void foo();
}

BusinessLogic

public class BusinessLogic implements IBusinessLogic {

	public void foo() 
    {
        System.out.println(
        "Inside BusinessLogic.foo()");
    }
}

TracingAfterAdvice.java

public class TracingAfterAdvice implements AfterReturningAdvice {

	public void afterReturning(Object arg0, Method arg1, Object[] arg2,
			Object arg3) throws Throwable {
		System.out.println(
		          "Hello world! (by " + 
		          this.getClass().getName() + 
		          ")");
	}

}

TracingBeforeAdvice.java

public class TracingBeforeAdvice implements MethodBeforeAdvice {

	public void before(Method arg0, Object[] arg1, Object arg2) throws Throwable {
		System.out.println(
		          "Hello world! (by " + 
		          this.getClass().getName() + 
		          ")");
	}

}

main

public class MainApplication {

	/**
	 * @param args
	 */
	public static void main(String[] args) {
//		 Read the configuration file
//       ApplicationContext ctx = new FileSystemXmlApplicationContext("springconfig.xml");
		
		ApplicationContext ctx = new ClassPathXmlApplicationContext("applicationContext.xml");
        //Instantiate an object
        IBusinessLogic testObject = (IBusinessLogic) ctx.getBean("businesslogicbean");

        // Execute the public 
        // method of the bean
        testObject.foo();
	}

}

希望还有下文....

就我自身用过的情况来说.
Around处理用得比较多,before,after比较少一些

AOP在项目中能够适用哪些情况呢？
用在权限的鉴权方面比较好，但是acegi框架这部分已经做的很好了，所以觉得AOP的用武之地不适很多。。。

想问一下Spring里面的功能，开发时能用到多少？

主要还是在用IOC,使用的多了，思维模式就越来越有spring味道了，
而AOP用的地方到不是很多，因为需要用的地方－如权限，都有现成的产品可以集成－如acegi

java里面有回调函数么？
我想利用AOP是否可以实现方法的回调，就像C#里面的委托一下
不知道是否可行