动态代理实现原理
装饰模式 vs (静态)代理模式中提到,在静态代理模式中，针对每个须要被代理的类都要在编译前就提早写好一个代理类，这样作增长了类管理的复杂性，若是咱们能够在运行期间动态的来生成这个代理类，就会方便不少，这就是动态代理模式的核心思想，也是Spring中AOP(Aspect Oriented Programming)的实现原理。动态代理有两种实现方法：jdk动态代理和cglib动态代理，下面分别来具体看一下：java
jdk动态代理
咱们知道，在java中若是想在运行期动态的生成一个类，就要借助反射机制。jdk动态代理就是经过java.lang.reflect.Proxy利用反射机制提供了一种原生的动态代理模式，它提供了一个静态方法：express
public static Object newProxyInstance(ClassLoader loader,
Class<?>[] interfaces,
InvocationHandler h)
throws IllegalArgumentException
{
Objects.requireNonNull(h);
final Class<?>[] intfs = interfaces.clone();
final SecurityManager sm = System.getSecurityManager();
if (sm != null) {
checkProxyAccess(Reflection.getCallerClass(), loader, intfs);
}
/*
* Look up or generate the designated proxy class.
*/
Class<?> cl = getProxyClass0(loader, intfs);
/*
* Invoke its constructor with the designated invocation handler.
*/
try {
if (sm != null) {
checkNewProxyPermission(Reflection.getCallerClass(), cl);
}
final Constructor<?> cons = cl.getConstructor(constructorParams);
final InvocationHandler ih = h;
if (!Modifier.isPublic(cl.getModifiers())) {
AccessController.doPrivileged(new PrivilegedAction<Void>() {
public Void run() {
cons.setAccessible(true);
return null;
}
});
}
return cons.newInstance(new Object[]{h});
} catch (IllegalAccessException|InstantiationException e) {
throw new InternalError(e.toString(), e);
} catch (InvocationTargetException e) {
Throwable t = e.getCause();
if (t instanceof RuntimeException) {
throw (RuntimeException) t;
} else {
throw new InternalError(t.toString(), t);
}
} catch (NoSuchMethodException e) {
throw new InternalError(e.toString(), e);
}
}
它的三个参数分别是：apache
- loader the class loader to define the proxy class
- interfaces the list of interfaces for the proxy class to implement
- the invocation handler to dispatch method invocations to
其中Class<?> cl = getProxyClass0(loader, intfs);最终会调用Proxy的内部类ProxyClassFactory，而后调用ProxyGenerator里的generateProxyClass生成Class字节码数组：segmentfault
public static byte[] generateProxyClass(final String var0, Class<?>[] var1, int var2) {
ProxyGenerator var3 = new ProxyGenerator(var0, var1, var2);
final byte[] var4 = var3.generateClassFile();
if (saveGeneratedFiles) {
AccessController.doPrivileged(new PrivilegedAction<Void>() {
public Void run() {
try {
int var1 = var0.lastIndexOf(46);
Path var2;
if (var1 > 0) {
Path var3 = Paths.get(var0.substring(0, var1).replace('.', File.separatorChar));
Files.createDirectories(var3);
var2 = var3.resolve(var0.substring(var1 + 1, var0.length()) + ".class");
} else {
var2 = Paths.get(var0 + ".class");
}
Files.write(var2, var4, new OpenOption[0]);
return null;
} catch (IOException var4x) {
throw new InternalError("I/O exception saving generated file: " + var4x);
}
}
});
}
return var4;
}
最后利用defineClass0(loader, proxyName,proxyClassFile, 0, proxyClassFile.length);返回类实例。而后利用这个类传入InvocationHandler参数构建一个代理类实例。
在运行当前main方法的路径下建立com/sun/proxy目录，并建立一个\$Proxy0.class文件，而后设置sun.misc.ProxyGenerator.saveGeneratedFiles系统属性为true，反编译\$Proxy0.class文件能够看到：数组
public final class $Proxy0 extends Proxy implements UserManager {
private static Method m1;
private static Method m3;
private static Method m0;
private static Method m2;
public $Proxy0(InvocationHandler paramInvocationHandler) {
super(paramInvocationHandler);
}
public final boolean equals(Object paramObject) {
try {
return ((Boolean)this.h.invoke(this, m1, new Object[] { paramObject })).booleanValue();
}
catch (Error|RuntimeException localError) {
throw localError;
}
catch (Throwable localThrowable) {
throw new UndeclaredThrowableException(localThrowable);
}
}
public final void addUser(String paramString) {
try {
this.h.invoke(this, m3, new Object[] { paramString });
return;
}
catch (Error|RuntimeException localError) {
throw localError;
}
catch (Throwable localThrowable) {
throw new UndeclaredThrowableException(localThrowable);
}
}
public final int hashCode() {
try {
return ((Integer)this.h.invoke(this, m0, null)).intValue();
}
catch (Error|RuntimeException localError) {
throw localError;
}
catch (Throwable localThrowable) {
throw new UndeclaredThrowableException(localThrowable);
}
}
public final String toString() {
try {
return (String)this.h.invoke(this, m2, null);
}
catch (Error|RuntimeException localError) {
throw localError;
}
catch (Throwable localThrowable) {
throw new UndeclaredThrowableException(localThrowable);
}
}
static {
try {
m1 = Class.forName("java.lang.Object").getMethod("equals", new Class[] { Class.forName("java.lang.Object") });
m3 = Class.forName("com.leon.proxy.UserManager").getMethod("addUser", new Class[] { Class.forName("java.lang.String") });
m0 = Class.forName("java.lang.Object").getMethod("hashCode", new Class[0]);
m2 = Class.forName("java.lang.Object").getMethod("toString", new Class[0]);
return;
}
catch (NoSuchMethodException localNoSuchMethodException) {
throw new NoSuchMethodError(localNoSuchMethodException.getMessage());
}
catch (ClassNotFoundException localClassNotFoundException) {
throw new NoClassDefFoundError(localClassNotFoundException.getMessage());
}
}
}
能够看到这个代理类里对于方法的调用都会去调用传入InvocationHandler的invoke方法。因此咱们只须要实现这个接口的invoke方法，就能够实现任意被代理类方法的拦截和扩展。最后附上示例代码：app
public interface UserManager {
void addUser(String userName);
}
public class UserManagerImpl implements UserManager {
@Override
public void addUser(String userName) {
System.out.println("Add user: " + userName);
}
}
public class LogHandler implements InvocationHandler {
private Object targetObject;
private Object newProxyInstance(Object targetObject){
this.targetObject=targetObject;
return Proxy.newProxyInstance(targetObject.getClass().getClassLoader(),
targetObject.getClass().getInterfaces(),this);
}
@Override
public Object invoke(Object proxy, Method method, Object[] args)
throws Throwable {
System.out.println("=========start=========");
Object ret=method.invoke(targetObject, args);
System.out.println("=========end=========");
return ret;
}
public static void main(String[] args){
LogHandler logHandler=new LogHandler();
UserManager userManager=(UserManager)logHandler.newProxyInstance(new UserManagerImpl());
userManager.addUser("Leon");
}
}
经过实现InvocationHandler接口，即可以对任意实现了接口的类进行代理，若是要对没有实现接口的类进行代理可使用下面的方法。less
cglib动态代理
经过cglib(Code Generation Library)第三方库来实现的动态代理，它的底层使用ASM(Java bytecode manipulation and analysis framework)利用继承的方法在内存中动态的生成被代理类的子类，解决了jdk动态代理要求被代理类必须实现接口的局限，且运行速度要远远快于jdk动态代理。下面假设UserManagerImpl没有实现接口：ide
public class UserManagerImpl {
public void addUser(String userName) {
System.out.println("Add user: " + userName);
}
}
首先实现一个MethodInterceptor接口，相似于InvocationHandler接口：ui
class LogInterceptor implements MethodInterceptor{
...
@Override
public Object intercept(Object obj, Method method, Object[] args, MethodProxy proxy) throws Throwable {
System.out.println("=========start=========");
Object ret = proxy.invokeSuper(obj, args);
System.out.println("=========end=========");
return ret;
}
}
而后利用cglib的Enhancer来生成代理类：this
Enhancer enhancer = new Enhancer();
enhancer.setSuperclass(UserManagerImpl.class);
enhancer.setCallback(new LogInterceptor());
UserManagerImpl userManagerImpl = (UserManagerImpl)enhancer.create();
userManagerImpl.addUser("Leon");
这里须要注意，因为是经过继承来实现代理，因此不能代理final类，也不能代理final方法。若是反编译生成的代理类，能够看到：
public class UserManagerImpl$$EnhancerByCGLIB$$e4856e83
extends UserManagerImpl
implements Factory
{
...
private MethodInterceptor CGLIB$CALLBACK_0;
...
public final String addUser(String userName)
{
...
MethodInterceptor var3= CGLIB$CALLBACK_0;
if (var3 != null) {
return (String)var3.intercept(this, CGLIB$addUser$0$Method, new Object[] {userName}, CGLIB$sayHello$0$Proxy);
}
return super.addUser(userName);
}
...
}
代理类继承了被代理类并实现了net.sf.cglib.proxy.Factor接口，执行方法是若是有MethodInterceptor就调用其intercept方法，若有没有就调用父类也就是被代理类方法。最后附上MethodInterceptor接口的定义：
/*
* Copyright 2002,2003 The Apache Software Foundation
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package net.sf.cglib.proxy;
/**
* General-purpose {@link Enhancer} callback which provides for "around advice".
* @author Juozas Baliuka <a href="mailto:baliuka@mwm.lt">baliuka@mwm.lt</a>
* @version $Id: MethodInterceptor.java,v 1.8 2004/06/24 21:15:20 herbyderby Exp $
*/
public interface MethodInterceptor
extends Callback
{
/**
* All generated proxied methods call this method instead of the original method.
* The original method may either be invoked by normal reflection using the Method object,
* or by using the MethodProxy (faster).
* @param obj "this", the enhanced object
* @param method intercepted Method
* @param args argument array; primitive types are wrapped
* @param proxy used to invoke super (non-intercepted method); may be called
* as many times as needed
* @throws Throwable any exception may be thrown; if so, super method will not be invoked
* @return any value compatible with the signature of the proxied method. Method returning void will ignore this value.
* @see MethodProxy
*/
public Object intercept(Object obj, java.lang.reflect.Method method, Object[] args,
MethodProxy proxy) throws Throwable;
}
相关文章
- 1. （转）JDK动态代理实现原理
- 2. 动态代理模式实现原理
- 3. JDK动态代理实现原理
- 4. jdk动态代理实现原理
- 5. java动态代理的实现原理
- 6. 动态代理实现原理----JDK1.8
- 7. java动态代理实现原理
- 8. JDK动态代理原理实现
- 9. CGLIB动态代理实现原理
- 10. 反射实现动态代理原理
- 更多相关文章...
- • Spring JDK动态代理（附带实例） - Spring教程
- • Spring CGLlB动态代理（附带实例） - Spring教程
- • Java Agent入门实战（三）-JVM Attach原理与使用
- • ☆技术问答集锦（13）Java Instrument原理
相关标签/搜索
每日一句
-
每一个你不满意的现在，都有一个你没有努力的曾经。
欢迎关注本站公众号,获取更多信息
相关文章
- 1. （转）JDK动态代理实现原理
- 2. 动态代理模式实现原理
- 3. JDK动态代理实现原理
- 4. jdk动态代理实现原理
- 5. java动态代理的实现原理
- 6. 动态代理实现原理----JDK1.8
- 7. java动态代理实现原理
- 8. JDK动态代理原理实现
- 9. CGLIB动态代理实现原理
- 10. 反射实现动态代理原理