Spring application has Cglib2AopProxy warnings

半腔热情 提交于 2019-11-30 03:55:18

Maybe you have extended JdbcDaoSupport and added @Transactional annotations.

You can set the Cglib2AopProxy logger to log level ERROR to avoid the warn messages. For example if using log4j and log4j.properties:

log.logger.org.springframework.aop.framework.Cglib2AopProxy = ERROR

This is most likely caused by the @Transactional annotation, Spring wraps your DAO in a proxy to add the transactional behavior.

I would recommend to make your DAO implement an Interface (create and use an interface for your DAO), this will allow Spring to use a JDK dynamic proxy instead of having to use CGLib.

Using CGLIB has a limitation that methods marked as final in target class can’t be advised as final methods can’t be overridden (CGLIB creates a subclass of target class at runtime) but this limitation disappears in case of using JDK dynamic proxies.

Reference

stokito

You should use interfaces for dependency injection, the most reasons for this are described here and here.

You can read documentation about proxying mechanic for details why you see this warning.

And please vote for feature request of inspection for IntelliJ that may helps us to avoid this warnings. BTW It also contains a good explanation.

Spring Boot now uses CGLIB proxying by default, including for the AOP support. If you need interface-based proxy, you’ll need to set the spring.aop.proxy-target-class to false.

spring.aop.proxy-target-class=false

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!