Spring AOP使用限制

最新推荐文章于 2025-07-04 02:01:06 发布

ef-dfef

最新推荐文章于 2025-07-04 02:01:06 发布

阅读量2k

点赞数 1

CC 4.0 BY-SA版权

分类专栏： Java

本文链接：https://blog.youkuaiyun.com/definite_things/article/details/42709867

Java 专栏收录该内容

5 篇文章

订阅专栏

本文探讨了Spring AOP框架的特点，特别是基于代理的AOP仅能拦截public方法的问题。若需拦截protected/private方法，则建议采用Spring支持的AspectJ编织技术。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

基于代理的AOP只会作用于public的方法。

Due to the proxy-based nature of Spring’s AOP framework, protected methods are by definition not intercepted, neither for JDK proxies (where this isn’t applicable) nor for CGLIB proxies (where this is technically possible but not recommendable for AOP purposes). As a consequence, any given pointcut will be matched against public methods only!

If your interception needs include protected/private methods or even constructors, consider the use of Spring-driven native AspectJ weaving instead of Spring’s proxy-based AOP framework. This constitutes a different mode of AOP usage with different characteristics, so be sure to make yourself familiar with weaving first before making a decision.

如果要作用于非public方法需要使用Load-time Weaving技术，这种技术不是JavaEE标准，所以需要针对特定环境配置，不利于扩展和维护。