When I launch the application, I get a lot of warnings in the lines of osaop.framework.Cglib2AopProxy 'Unable to proxy method [public final void org.springframework.jdbc.core.support.JdbcDaoSupport.setDataSource(javax.sql.DataSource)] because it is final: All calls to this method via a proxy will be routed directly to the proxy.' for about a dozen functions.
Now I understand very well that proxy-based aspects cannot be applied to final methods. However, I (at least I don't intend) tried to weave any aspects into JdbcDaoSupport . I suspect this comes from <tx:annotation-driven /> . Is there anything I can do to silence these warnings or, even better, to exclude these classes from the weaving aspect?
spring spring-aop spring-transactions
Michael Piefel Oct 02 2018-12-12T00: 00Z
source share