Spring 创建 JDK- and CGLIB-based proxies的区别

最新推荐文章于 2022-08-12 11:03:04 发布

原创最新推荐文章于 2022-08-12 11:03:04 发布 · 1.8k 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#aop #Spring

JAVA 专栏收录该内容

9 篇文章

订阅专栏

本文详细介绍了Spring AOP中代理对象的创建机制。主要包括：当目标对象未实现任何接口时，会使用CGLIB代理；如果目标类实现了至少一个接口且没有明确指定代理接口，则会自动使用JDK动态代理；当明确设置了代理接口属性时，无论目标类是否实现接口，都将使用JDK动态代理；最后，如果配置了proxyTargetClass为true，将强制使用CGLIB代理。

几条原则：

If the class of a target object that is to be proxied (hereafter simply referred to as the target class) doesn't implement any interfaces, then a CGLIB-based proxy will be created.【原因是：This is the easiest scenario, because JDK proxies are interface based, and no interfaces means JDK proxying isn't even possible. 】
If the proxyTargetClass property of the ProxyFactoryBean has been set to true, then a CGLIB-based proxy will be created. 【无视ProxyFactoryBean的属性proxyInterfaces是否有设置成为某一个或多个接口名】
If the proxyInterfaces property of the ProxyFactoryBean has been set to one or more fully qualified interface names, then a JDK-based proxy will be created.
If the proxyInterfaces property of the ProxyFactoryBean has not been set but the target class does implement one (or more) interfaces, then the ProxyFactoryBean will auto-detect the fact that the target class does actually implement at least one interface, and a JDK-based proxy will be created, or a CGLIB-based proxy will be created.【如果是JDK代理这一条和第三条行为一致】