Spring AOP does not intercept methods within Spring's container

Question

I am new to Spring AOP. Using annotation based Spring configuration: @Configuration @EnableAspectJAutoProxy(proxyTargetClass=true) @ComponentScan({"sk.lkrnac"}) Aspect: @Aspect @Component public class TestAspect { @Before("execution(* *(..))") public void logJoinPoint(JoinPoint joinPoint){ .... } } Spring compoment: package sk.lkrnac.testaop; @Component public class TestComponent{ @PostConstruct public void init(){ testMethod(); } public void testMethod() { return; } } How can I intercept all public methods that are called by Spring framework itself? (e.g. TestComponent.init() during creation of the TestComponent instance by Spring) Currently I am able to intercept only TestComponent.testMethod() by invoking: TestComponent testComponent = springContext.getBean(TestComponent.class); testComponent.testMethod(); JavaScript questions and answers, JavaScript questions pdf, JavaScript question bank, JavaScript questions and answers pdf, mcq on JavaScript pdf, JavaScript questions and solutions, JavaScript mcq Test , Interview JavaScript questions, JavaScript Questions for Interview, JavaScript MCQ (Multiple Choice Questions)

Answer 1

This is a common issue you run into with Spring AOP. Spring accomplishes AOP by proxying advised classes. In your case, your TestComponent instances will be wrapped in a run-time proxy class that provides the "hooks" for any aspect advice to be applied. This works very well when methods are called from outside the class, but as you have discovered it doesn't work on internal calls. The reason is that internal calls will not pass the proxy barrier, thus will not trigger the aspect. There are primarily two ways around this. One is to fetch an instance of the (proxied) bean from the context. This is what you have already tried with success. The other way is to use something called load-time weaving. When using this, AOP advices are added to a class ("weaved" into it) by a custom class-loader by injecting byte-code into the class definition. The Spring documentation has more on this. There is a third way, which is called "compile time weaving". In this scenario, your AOP advices are statically weaved into each advised class when you compile it.