Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

spring-projects-issues opened this issue Feb 11, 2014 · 1 comment


Copy link

@spring-projects-issues spring-projects-issues commented Feb 11, 2014

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:

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

Referenced from: commits 9493380

Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Feb 12, 2014

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants