Ignore container callback and marker interfaces for auto-proxy decisions [SPR-11416]

[spring-projects-issues]

Juergen Hoeller opened SPR-11416 and commented

Spring's auto-proxy creation infrastructure currently switches to a target-class proxy only if it has been explicitly requested or if no interfaces are being implemented at all. We should be smarter here and ignore container callback and marker interfaces for that decision, falling back to a target-class proxy even when BeanFactoryAware, InitializingBean etc are the only interfaces being implemented.

---

Affects: 4.0.1

Issue Links:

• Test instances should not be proxied in the TestContext framework [SPR-9478] #14113 Test instances should not be proxied in the TestContext framework
• Improve error reporting for issues related to @Controller types requiring AOP proxing [SPR-11281] #15905 Improve error reporting for issues related to @Controller types requiring AOP proxing

Referenced from: commits 9493380

[spring-projects-issues]

Sam Brannen commented

Please note that the resolution of this issue prior to #14113 may cause CGLIB-related memory issues to become more common in transactional integration testing scenarios, since subclasses of AbstractTransactionalJUnit4SpringContextTests and AbstractTransactionalTestNGSpringContextTests will now be proxied by class instead of via the ApplicationContextAware interface.