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

Spring MVC and AOP: @EnableAspectJAutoProxy needs to be redeclared for each application context [SPR-14753] #19319

spring-issuemaster opened this issue Sep 26, 2016 · 0 comments


Copy link

@spring-issuemaster spring-issuemaster commented Sep 26, 2016

Manuel Jordan opened SPR-14753 and commented


According with the following:

Why the class annotated with @EnableAspectJAutoProxy and scanned through RootApplicationContext is practically ignored by ServletApplicationContext?

Exists two possible solutions:

  • the class annotated with @EnableAspectJAutoProxy should be scanned through ServletApplicationContext instead
  • the class annotated with @EnableAspectJAutoProxy should be scanned twice, by RootApplicationContext and ServletApplicationContext

I think each approach has a drawback

Furthermore from the current answer:

Seems that BeanFactoryPostProcessor (which is @EnableAspectJAutoProxy in your case) from parent context not applied to child contexts. To make it work in production you must explicitly define @EnableAspectJAutoProxy in child context too

If that is true is it a bug or is the expected behaviour?

Your explanation about this situation with the solution (extra configuration if exists) should be added in the Spring Framework Reference Documentation, it for the rest of the community.

I think here we have a situation about Best Practices

Thanks by your understanding.

Affects: 4.3 GA

Reference URL:

Issue Links:

  • #20356 Doc: Spring AOP dependency on aspectjweaver
  • #21392 Spring MVC: @EnableScheduling needs to be redeclared for each application context

Referenced from: commits 0e734d8, 13c2134

Backported to: 4.3.15

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.