学步园

1.处理AOP配置的通知基本步骤：

(1).获取AOP配置的通知Advice：

从上一篇博客《创建AOP代理对象并对目标对象切面拦截》对Spring中采用JDK和CGLIB两种方式创建AOP动态代理的源码分析中，我们了解到，在AOP动态代理对象的回调方法中，都需要使用以下方式获取AOP配置的通知，并将获取到的通知和目标对象、代理对象等一起封装为ReflectiveMethodInvocation对象：

//获取AOP配置的通知<br /> List<Object> chain = this.advised.getInterceptorsAndDynamicInterceptionAdvice(method, targetClass);<br /> ……<br /> //根据获取的通知、目标对象等创建ReflectiveMethodInvocation<br /> //如果是CGLIB方式，则创建CglibMethodInvocation对象:<br /> //new CglibMethodInvocation(proxy, target, method, args, targetClass, chain, methodProxy);<br /> invocation = new ReflectiveMethodInvocation(proxy, target, method, args, targetClass, chain);<br /> //沿着获取的通知链，递归调用所有配置的AOP通知<br /> retVal = invocation.proceed();<br />

(2).创建ReflectiveMethodInvocation对象：

a.创建CglibMethodInvocation对象：

//CglibMethodInvocation的构造方法<br /> public CglibMethodInvocation(Object proxy, Object target, Method method, Object[] arguments,<br /> Class targetClass, List<Object> interceptorsAndDynamicMethodMatchers, MethodProxy methodProxy) {<br /> //调用父类ReflectiveMethodInvocation的构造方法<br /> super(proxy, target, method, arguments, targetClass, interceptorsAndDynamicMethodMatchers);<br /> this.methodProxy = methodProxy;<br /> this.protectedMethod = Modifier.isProtected(method.getModifiers());<br /> }<br />

CglibMethodInvocation继承ReflectiveMethodInvocation类，在创建时首先调用父类的初始化方法。

b.创建ReflectiveMethodInvocation对象：

//ReflectiveMethodInvocation的构造方法<br /> protected ReflectiveMethodInvocation(<br /> Object proxy, Object target, Method method, Object[] arguments,<br /> Class targetClass, List<Object> interceptorsAndDynamicMethodMatchers) {<br /> this.proxy = proxy;<br /> this.target = target;<br /> this.targetClass = targetClass;<br /> this.method = BridgeMethodResolver.findBridgedMethod(method);<br /> this.arguments = arguments;<br /> //将获取到的AOP通知赋值给成员变量<br /> this.interceptorsAndDynamicMethodMatchers = interceptorsAndDynamicMethodMatchers;<br /> }<br />

(3).处理AOP配置的通知器：

Spring通过调用ReflectiveMethodInvocation类来处理AOP配置的通知，CglibMethodInvocation继承ReflectiveMethodInvocation，因此JDK和CGLIB方式都是通过调用ReflectiveMethodInvocation的proceed()方法来处理通知的，处理通知的源码如下：

//处理AOP配置的通知<br /> public Object proceed() throws Throwable {<br /> //如果拦截器链中通知已经调用完毕<br /> if (this.currentInterceptorIndex == this.interceptorsAndDynamicMethodMatchers.size() - 1) {<br /> //这个方法调用AopUtils.invokeJoinpointUsingReflection方法，<br /> //通过反射机制直接调用目标对象方法<br /> return invokeJoinpoint();<br /> }<br /> //获取AOP配置的通知，在ReflectiveMethodInvocation初始化构方法中将获<br /> //取到的AOP通知赋值给interceptorsAndDynamicMethodMatchers变量<br /> Object interceptorOrInterceptionAdvice = this.interceptorsAndDynamicMethodMatchers.get(++this.currentInterceptorIndex);<br /> //如果获取的通知器或通知是动态匹配方法拦截器类型<br /> if (interceptorOrInterceptionAdvice instanceof InterceptorAndDynamicMethodMatcher) {<br /> //动态匹配方法拦截器<br /> InterceptorAndDynamicMethodMatcher dm =<br /> (InterceptorAndDynamicMethodMatcher) interceptorOrInterceptionAdvice;<br /> if (dm.methodMatcher.matches(this.method, this.targetClass, this.arguments)) {<br /> //如果匹配，调用拦截器的方法<br /> return dm.interceptor.invoke(this);<br /> }<br /> else {<br /> //如果不匹配，递归调用proceed()方法，知道拦截器链被全部调用为止<br /> return proceed();<br /> }<br /> }<br /> else {<br /> //如果不是动态匹配方法拦截器，则切入点在构造对象之前进行静态匹配，调用<br /> //拦截器的方法<br /> return ((MethodInterceptor) interceptorOrInterceptionAdvice).invoke(this);<br /> }<br /> }<br />

2.AOP代理创建辅助类AdvisedSupport获取通知：

在1中我们看到，获取AOP通知的的方法如下：

List<Object> chain = this.advised.getInterceptorsAndDynamicInterceptionAdvice(method, targetClass);

该方法会通过AOP代理创建辅助类AdvisedSupport获取AOP配置的通知，获取通知的过程如下：

(1).AdvisedSupport获取给定方法的通知：

//获取通知<br /> public List<Object> getInterceptorsAndDynamicInterceptionAdvice(Method method, Class targetClass) {<br /> //使用cache缓存<br /> MethodCacheKey cacheKey = new MethodCacheKey(method);<br /> //首先从缓存中获取<br /> List<Object> cached = this.methodCache.get(cacheKey);<br /> //如果缓存中没有，即第一次调用<br /> if (cached == null) {<br /> //从通知器链容器中获取通知，这里使用的DefaultAdvisorChainFactory<br /> cached = this.advisorChainFactory.getInterceptorsAndDynamicInterceptionAdvice(<br /> this, method, targetClass);<br /> //缓存获取到的通知<br /> this.methodCache.put(cacheKey, cached);<br /> }<br /> return cached;<br /> }<br />

通过上面的源码我们看到，AdvisedSupport第一次获取通知时，会从通知链容器DefaultAdvisorChainFactory中通过getInterceptorsAndDynamicInterceptionAdvice方法获取指定的通知。

(2).DefaultAdvisorChainFactory获取指类，指定方法的通知：

DefaultAdvisorChainFactory通过getInterceptorsAndDynamicInterceptionAdvice方法获取指定类中指定方法的通知，源码如下：

//获取通知<br /> public List<Object> getInterceptorsAndDynamicInterceptionAdvice(<br /> Advised config, Method method, Class targetClass) {<br /> //根据AOP中配置的通知器创建一个保持获取到通知的集合<br /> List<Object> interceptorList = new ArrayList<Object>(config.getAdvisors().length);<br /> //判断目标类中是否引入了配置的通知<br /> boolean hasIntroductions = hasMatchingIntroductions(config, targetClass);<br /> //获取通知适配器注册单态模式对象<br /> AdvisorAdapterRegistry registry = GlobalAdvisorAdapterRegistry.getInstance();<br /> //遍历AOP配置的通知<br /> for (Advisor advisor : config.getAdvisors()) {<br /> //如果通知器的类型是切入点通知器<br /> if (advisor instanceof PointcutAdvisor) {<br /> PointcutAdvisor pointcutAdvisor = (PointcutAdvisor) advisor;<br /> //如果AOP配置对通知已经过滤，即只包含符合条件的通知器，或者<br /> //获取当前切入点的类过滤器匹配目标类<br /> if (config.isPreFiltered() || pointcutAdvisor.getPointcut().getClassFilter().matches(targetClass)) { //获取通知器中的方法拦截器列表<br /> MethodInterceptor[] interceptors = registry.getInterceptors(advisor);<br /> //获取当前通知器切入点的方法匹配器<br /> MethodMatcher mm = pointcutAdvisor.getPointcut().getMethodMatcher();<br /> //如果目标类的方法匹配切入点<br /> if (MethodMatchers.matches(mm, method, targetClass, hasIntroductions)) {<br /> //如果方法匹配器是运行时动态匹配的<br /> if (mm.isRuntime()) {<br /> //将通知器中的方法拦截器和方法匹配器封装后添加到返回的通知器集合中<br /> for (MethodInterceptor interceptor : interceptors) {<br /> interceptorList.add(new InterceptorAndDynamicMethodMatcher(interceptor, mm));<br /> }<br /> }<br /> //如果方法匹配器是静态的，则将方法拦截器直接添加到返回的通知器集合中<br /> else {<br /> interceptorList.addAll(Arrays.asList(interceptors));<br /> }<br /> }<br /> }<br /> }<br /> //如果通知器类型是引入通知器<br /> else if (advisor instanceof IntroductionAdvisor) {<br /> IntroductionAdvisor ia = (IntroductionAdvisor) advisor;<br /> //如果AOP通知配置是预过滤的，或者目标类符合当前通知器的类过滤器<br /> if (config.isPreFiltered() || ia.getClassFilter().matches(targetClass)) {<br /> //获取通知器中所有的方法拦截器，即通知<br /> Interceptor[] interceptors = registry.getInterceptors(advisor);<br /> //将通知添加到要返回的通知集合中<br /> interceptorList.addAll(Arrays.asList(interceptors));<br /> }<br /> }<br /> //如果通知类型既不是切入点通知器，又不是引入通知器<br /> else {<br /> Interceptor[] interceptors = registry.getInterceptors(advisor);<br /> //直接将通知添加到要返回的通知集合中<br /> interceptorList.addAll(Arrays.asList(interceptors));<br /> }<br /> }<br /> return interceptorList;<br /> }<br /> //检查目标类和AOP通知配置是否匹配AOP引入规则<br /> private static boolean hasMatchingIntroductions(Advised config, Class targetClass) {<br /> //遍历所有的通知器<br /> for (int i = 0; i < config.getAdvisors().length; i++) {<br /> Advisor advisor = config.getAdvisors()[i];<br /> //如果通知器是引入通知器<br /> if (advisor instanceof IntroductionAdvisor) {<br /> IntroductionAdvisor ia = (IntroductionAdvisor) advisor;<br /> //使用当前通知器的类过滤器匹配目标类<br /> if (ia.getClassFilter().matches(targetClass)) {<br /> return true;<br /> }<br /> }<br /> }<br /> return false;<br /> }<br />

通过上面DefaultAdvisorChainFactory获取通知过程源码的分析，我们看到通过AdvisorAdapterRegistry的getInterceptors方法获取通知器的通知，AdvisorAdapterRegistry是一个接口，具体的实现交由其实现类DefaultAdvisorAdapterRegistry提供。

3.DefaultAdvisorAdapterRegistry获取通知器的通知：

DefaultAdvisorAdapterRegistry的源码如下：

public class DefaultAdvisorAdapterRegistry implements AdvisorAdapterRegistry, Serializable {<br /> //持有通知适配器的集合<br /> private final List<AdvisorAdapter> adapters = new ArrayList<AdvisorAdapter>(3);<br /> //构造方法，为通知适配器集合添加Spring的3种类型通知适配器<br /> public DefaultAdvisorAdapterRegistry() {<br /> registerAdvisorAdapter(new MethodBeforeAdviceAdapter());<br /> registerAdvisorAdapter(new AfterReturningAdviceAdapter());<br /> registerAdvisorAdapter(new ThrowsAdviceAdapter());<br /> }<br /> //将通知封装为通知器<br /> public Advisor wrap(Object adviceObject) throws UnknownAdviceTypeException {<br /> //如果通知对象是通知器类型，则不用封装<br /> if (adviceObject instanceof Advisor) {<br /> return (Advisor) adviceObject;<br /> }<br /> if (!(adviceObject instanceof Advice)) {<br /> throw new UnknownAdviceTypeException(adviceObject);<br /> }<br /> Advice advice = (Advice) adviceObject;<br /> //如果通知是方法拦截器<br /> if (advice instanceof MethodInterceptor) {<br /> //将方法拦截器类型的通知封装为默认切入点通知器<br /> return new DefaultPointcutAdvisor(advice);<br /> }<br /> for (AdvisorAdapter adapter : this.adapters) {<br /> //检查通知适配器是否支持给定的通知<br /> if (adapter.supportsAdvice(advice)) {<br /> return new DefaultPointcutAdvisor(advice);<br /> }<br /> }<br /> throw new UnknownAdviceTypeException(advice);<br /> }<br /> //获取通知器的通知<br /> public MethodInterceptor[] getInterceptors(Advisor advisor) throws UnknownAdviceTypeException {<br /> List<MethodInterceptor> interceptors = new ArrayList<MethodInterceptor>(3);<br /> //通知通知器的通知<br /> Advice advice = advisor.getAdvice();<br /> //如果通知是方法拦截器类型，则不需要适配，直接添加到通知集合中<br /> if (advice instanceof MethodInterceptor) {<br /> interceptors.add((MethodInterceptor) advice);<br /> }<br /> //对通知进行适配，从适配器中获取封装好AOP编制功能的拦截器<br /> for (AdvisorAdapter adapter : this.adapters) {<br /> if (adapter.supportsAdvice(advice)) {<br /> interceptors.add(adapter.getInterceptor(advisor));<br /> }<br /> }<br /> if (interceptors.isEmpty()) {<br /> throw new UnknownAdviceTypeException(advisor.getAdvice());<br /> }<br /> return interceptors.toArray(new MethodInterceptor[interceptors.size()]);<br /> }<br /> //注册通知适配器<br /> public void registerAdvisorAdapter(AdvisorAdapter adapter) {<br /> this.adapters.add(adapter);<br /> }<br /> }<br />

从上述代码获取通知源码分析中我们看到，DefaultAdvisorAdapterRegistry的getInterceptors方法中，需要将AOP配置的通知封装为通知适配器，下面我们继续分析通知适配器的主要源码和功能。

4.通知适配器：

通知适配器AdvisorAdapter对通知进行封装，为通知提供Spring
AOP的增强功能，下面我们以MethodBeforeAdviceAdapter为例，分析通知适配器的具体功能：

(1).MethodBeforeAdviceAdapter源码：

class MethodBeforeAdviceAdapter implements AdvisorAdapter, Serializable {<br /> //检查通知是否为通知适配器适配的通知类型<br /> public boolean supportsAdvice(Advice advice) {<br /> return (advice instanceof MethodBeforeAdvice);<br /> }<br /> //获取通知拦截器<br /> public MethodInterceptor getInterceptor(Advisor advisor) {<br /> //获取通知器的通知<br /> MethodBeforeAdvice advice = (MethodBeforeAdvice) advisor.getAdvice();<br /> //将通知封装为方法拦截器<br /> return new MethodBeforeAdviceInterceptor(advice);<br /> }<br /> }<br />

通过对MethodBeforeAdviceAdapter的源码分析，我们看到通知适配器在获取到通知器的通知后，将通知封装为方法拦截器，我们接下来分析MethodBeforeAdviceInterceptor是如何将通知封装为方法拦截器的。

(2).MethodBeforeAdviceInterceptor封装通知：

MethodBeforeAdviceInterceptor封装通知实现了Spring
AOP的织入功能，其源码如下：

public class MethodBeforeAdviceInterceptor implements MethodInterceptor, Serializable {<br /> private MethodBeforeAdvice advice;<br /> //拦截器构造方法，初始化通知<br /> public MethodBeforeAdviceInterceptor(MethodBeforeAdvice advice) {<br /> Assert.notNull(advice, "Advice must not be null");<br /> this.advice = advice;<br /> }<br /> //拦截器的回调方法，会在代理对象的方法调用前触发回调<br /> public Object invoke(MethodInvocation mi) throws Throwable {<br /> //在目标方法调用之前，先调用前置通知的before方法<br /> this.advice.before(mi.getMethod(), mi.getArguments(), mi.getThis() );<br /> //继续调用通知拦截链，调用ReflectiveMethodInvocation的proceed方法<br /> return mi.proceed();<br /> }<br /> }<br />

通过对MethodBeforeAdviceInterceptor拦截器的源码分析，我们看到，Spring对AOP处理的基本流程：

首先，为目标对象对象创建AOP代理对象，根据AOP配置获取通知器，通知器中持有切入点和通知。

其次，根据通知器中的切入点，获取目标类目标方法的通知，并将通知封装为拦截器，添加到代理拦截链中。

最后，调用目标对象目标方法时，调用AOP代理对象，根据通知在调用目标对象方法时触发调用通知链中通知拦截器的回调方法。

5.方法拦截器：

在4中我们已经分析了MethodBeforeAdviceInterceptor源码，了解到方法拦截器主要作用是根据通知类型在调用目标方法时触发通知的回调，我们接下来分析AfterReturningAdviceInterceptor和ThrowsAdviceInterceptor拦截器的源码，了解对后置通知和异常通知的处理实现：

(1).AfterReturningAdviceInterceptor:

public class AfterReturningAdviceInterceptor implements MethodInterceptor, AfterAdvice, Serializable {<br /> private final AfterReturningAdvice advice;<br /> //后置通知拦截器构造方法，初始化通知<br /> public AfterReturningAdviceInterceptor(AfterReturningAdvice advice) {<br /> Assert.notNull(advice, "Advice must not be null");<br /> this.advice = advice;<br /> }<br /> //后置通知拦截器回调方法<br /> public Object invoke(MethodInvocation mi) throws Throwable {<br /> //调用ReflectiveMethodInvocation的proceed方法，调用通知链<br /> Object retVal = mi.proceed();<br /> //通知链调用最后才调用后置通知的返回之后回调方法<br /> this.advice.afterReturning(retVal, mi.getMethod(), mi.getArguments(), mi.getThis());<br /> return retVal;<br /> }<br /> }<br />

(2).ThrowsAdviceInterceptor：

异常通知拦截器ThrowsAdviceInterceptor和前置通知拦截器MethodBeforeAdviceInterceptor、后置通知拦截器AfterReturningAdviceInterceptor类似，不同之处在于需要维护异常处理器，因此更加复杂，源码如下：

public class ThrowsAdviceInterceptor implements MethodInterceptor, AfterAdvice {<br /> private static final String AFTER_THROWING = "afterThrowing";<br /> private static final Log logger = LogFactory.getLog(ThrowsAdviceInterceptor.class);<br /> private final Object throwsAdvice;<br /> //key为类，value为method的异常处理map<br /> private final Map<Class, Method> exceptionHandlerMap = new HashMap<Class, Method>();<br /> //异常通知拦截器构造方法<br /> public ThrowsAdviceInterceptor(Object throwsAdvice) {<br /> Assert.notNull(throwsAdvice, "Advice must not be null");<br /> //初始化异常通知<br /> this.throwsAdvice = throwsAdvice;<br /> //获取异常通知的方法<br /> Method[] methods = throwsAdvice.getClass().getMethods();<br /> //遍历所有配置异常通知的方法<br /> for (Method method : methods) {<br /> //如果方法名为"afterThrowing"，且方法参数为1或4，且方法参数的父类为<br /> //Throwable，说明异常通知中有异常处理器<br /> if (method.getName().equals(AFTER_THROWING) &&<br /> (method.getParameterTypes().length == 1 || method.getParameterTypes().length == 4) &&<br /> Throwable.class.isAssignableFrom(method.getParameterTypes()[method.getParameterTypes().length - 1])<br /> ) {<br /> //添加异常处理器<br /> this.exceptionHandlerMap.put(method.getParameterTypes()[method.getParameterTypes().length - 1], method);<br /> if (logger.isDebugEnabled()) {<br /> logger.debug("Found exception handler method: " + method);<br /> }<br /> }<br /> }<br /> //没有配置异常处理器<br /> if (this.exceptionHandlerMap.isEmpty()) {<br /> throw new IllegalArgumentException(<br /> "At least one handler method must be found in class [" + throwsAdvice.getClass() + "]");<br /> }<br /> }<br /> //获取异常处理器数目<br /> public int getHandlerMethodCount() {<br /> return this.exceptionHandlerMap.size();<br /> }<br /> //获取异常处理器<br /> private Method getExceptionHandler(Throwable exception) {<br /> //获取给定异常类<br /> Class exceptionClass = exception.getClass();<br /> if (logger.isTraceEnabled()) {<br /> logger.trace("Trying to find handler for exception of type [" + exceptionClass.getName() + "]");<br /> }<br /> //从异常处理器map中获取给定异常类的处理器<br /> Method handler = this.exceptionHandlerMap.get(exceptionClass);<br /> //如果异常处理器为null，且异常类不是Throwable<br /> while (handler == null && !exceptionClass.equals(Throwable.class)) {<br /> //获取异常类的基类<br /> exceptionClass = exceptionClass.getSuperclass();<br /> //获取基类的异常处理器<br /> handler = this.exceptionHandlerMap.get(exceptionClass);<br /> }<br /> if (handler != null && logger.isDebugEnabled()) {<br /> logger.debug("Found handler for exception of type [" + exceptionClass.getName() + "]: " + handler);<br /> }<br /> return handler;<br /> }<br /> //异常通知的回调方法<br /> public Object invoke(MethodInvocation mi) throws Throwable {<br /> //把目标对象方法调用放入try/catch中<br /> try {<br /> return mi.proceed();<br /> }<br /> catch (Throwable ex) {<br /> //在catch中触发异常通知的回调<br /> Method handlerMethod = getExceptionHandler(ex);<br /> if (handlerMethod != null) {<br /> //使用异常处理器处理异常<br /> invokeHandlerMethod(mi, ex, handlerMethod);<br /> }<br /> //将异常向上抛出<br /> throw ex;<br /> }<br /> }<br /> //异常处理器处理异常<br /> private void invokeHandlerMethod(MethodInvocation mi, Throwable ex, Method method) throws Throwable {<br /> Object[] handlerArgs;<br /> //如果方法只有一个参数<br /> if (method.getParameterTypes().length == 1) {<br /> handlerArgs = new Object[] { ex };<br /> }<br /> //获取方法的参数列表<br /> else {<br /> handlerArgs = new Object[] {mi.getMethod(), mi.getArguments(), mi.getThis(), ex};<br /> }<br /> try {<br /> //使用JDK反射机制，调用异常通知的异常处理方法<br /> method.invoke(this.throwsAdvice, handlerArgs);<br /> }<br /> catch (InvocationTargetException targetEx) {<br /> throw targetEx.getTargetException();<br /> }<br /> }<br /> }<br />

6.ProxyFactory实现编程式AOP:

在上一篇博客《创建AOP代理对象并对目标对象切面拦截》中，我们以ProxyFactoryBean
为例，分析了Spring创建AOP代理对象以及对目标对象进行切面拦截的实现过程，在Spring中还有另一个创建AOP代理对象的容器——ProxyFactory，两个创建AOP代理对象容器的区别如下：

a.ProxyFactory：创建编程式的Spring
AOP应用。

b.ProxyFactoryBean：创建声明式的Spring
AOP应用。

我们现在通过分析ProxyFactory源码，了解Spring编程式AOP应用的具体实现：

(1).使用ProxyFactory编程式AOP应用的简单例子：

//获取目标对象<br /> TargetImpl target = new TargetImpl();<br /> //创建目标对象的代理工厂<br /> ProxyFactory aopFactory = new ProxyFactory(target);<br /> //为目标对象代理工厂添加通知器<br /> aopFactory.addAdvisor(要添加的Advisor);<br /> //为目标对象代理工厂添加通知<br /> aopFactory.addAdvice(要添加的Advice);<br /> //获取目标对象的代理<br /> TargetImpl targetProxy = (TargetImpl)aopFactory.getProxy();<br />

(2).ProxyFactory源码：

public class ProxyFactory extends ProxyCreatorSupport {<br /> //创建一个空的AOP代理容器<br /> public ProxyFactory() {<br /> }<br /> //为目标对象创建AOP代理容器<br /> public ProxyFactory(Object target) {<br /> Assert.notNull(target, "Target object must not be null");<br /> setInterfaces(ClassUtils.getAllInterfaces(target));<br /> setTarget(target);<br /> }<br /> //根据代理接口创建AOP代理容器<br /> public ProxyFactory(Class[] proxyInterfaces) {<br /> setInterfaces(proxyInterfaces);<br /> }<br /> //为指定代理接口和拦截器创建AOP代理容器<br /> public ProxyFactory(Class proxyInterface, Interceptor interceptor) {<br /> //为代理对象添加代理接口<br /> addInterface(proxyInterface);<br /> //为代理对象添加拦截器<br /> addAdvice(interceptor);<br /> }<br /> //根据指定目标源和代理接口创建代理容器<br /> public ProxyFactory(Class proxyInterface, TargetSource targetSource) {<br /> addInterface(proxyInterface);<br /> //为通知设置目标源<br /> setTargetSource(targetSource);<br /> }<br /> //获取AOP代理<br /> public Object getProxy() {<br /> return createAopProxy().getProxy();<br /> }<br /> //使用指定类加载器创建AOP代理<br /> public Object getProxy(ClassLoader classLoader) {<br /> return createAopProxy().getProxy(classLoader);<br /> }<br /> //获取指定代理接口和拦截器的AOP代理<br /> public static <T> T getProxy(Class<T> proxyInterface, Interceptor interceptor) {<br /> return (T) new ProxyFactory(proxyInterface, interceptor).getProxy();<br /> }<br /> //获取指定代理接口和目标源的AOP代理<br /> public static <T> T getProxy(Class<T> proxyInterface, TargetSource targetSource) {<br /> return (T) new ProxyFactory(proxyInterface, targetSource).getProxy();<br /> }<br /> //为指定目标源创建AOP代理<br /> public static Object getProxy(TargetSource targetSource) {<br /> if (targetSource.getTargetClass() == null) {<br /> throw new IllegalArgumentException("Cannot create class proxy for TargetSource with null target class");<br /> }<br /> ProxyFactory proxyFactory = new ProxyFactory();<br /> proxyFactory.setTargetSource(targetSource);<br /> proxyFactory.setProxyTargetClass(true);<br /> return proxyFactory.getProxy();<br /> }<br /> }<br />

通过上述对ProxyFactory源码的分析可以看出，获取代理对象的getProxy()方法中，调用ProxyCreatorSupport的createAopProxy()方法获得DefaultAopProxyFactory对象，通过调用DefaultAopProxyFactory类的createAopProxy方法来调用JDK或者CGLIB创建AOP代理对象，与ProxyFactoryBean实现原理相同，通知的配置以及方法的通知链拦截调用等都与ProxyFactoryBean完全相同，这里不再赘述，请实现参考上一篇博客对ProxyFactoryBean的分析。