execution Vs. call Join point

by

Acutally the explanation is quite simple if you understand the basic difference between call() and execution() pointcuts: While the former intercepts all callers (i.e. the sources of method calls), the latter intercepts the calls themselves no matter where they originate from.

So how can the number of interceptions triggered by both pointcuts differ?

  • If you call JRE/JDK methods from your own code, AspectJ can weave into your calls, but not into the execution joinpoints within the JDK (unless you have created a woven JDK as a preparatory step). Thus, the number of calls will be higher than the number of executions.
  • Similarly, if you call methods in third party libraries which you have not woven with AspectJ because they were not on the in-path during LTW or CTW, again the executions will not be captured.
  • Last, but not least, it can happen the other way around if your own woven code is called by third party libs or by JRE/JDK classes. In this case the counted number of executions will be higher than the number of calls because they originate from places outside the control of your AspectJ code.

Generally, in all cases the reason is the difference between overall used code and the subset of woven code. In other words: the difference between code under and beyond your (or the aspects’) control.

More Related Contents:

  1. @AspectJ pointcut for all methods of a class with specific annotation
  2. How to use AOP with AspectJ for logging?
  3. What is aspect-oriented programming?
  4. Use of proxies in Spring AOP
  5. Spring autowired bean for @Aspect aspect is null
  6. Spring AOP Advice on Annotated Controllers
  7. AspectJ pointcut expression match parameter annotations at any position
  8. Aspectj overwrite an argument of a method
  9. Configuring AspectJ aspects using Spring IoC with JavaConfig?
  10. Emulate annotation inheritance for interfaces and methods with AspectJ
  11. Spring autowiring using @Configurable
  12. NOT using repository pattern, use the ORM as is (EF)
  13. Tracking down cause of Spring’s “not eligible for auto-proxying”
  14. Get AOP proxy from the object itself
  15. How to inject an attribute using a PostSharp attribute?
  16. spring creates proxy for wrong classes when using aop class level annotation
  17. Is there any attribute relating to AJAX to be set for ASP.NET MVC controller actions?
  18. Traditional logging vs AOP logging
  19. Using Instrumentation to record unhandled exception
  20. Uncatchable ChuckNorrisException
  21. Performance impact of using aop
  22. java.lang.IllegalStateException: No thread-bound request found, exception in aspect
  23. Get value of a parameter of an annotation in Java
  24. Ruby dependency injection libraries
  25. logging with AOP in spring?
  26. Spring: register advice programmatically at runtime
  27. Spring AOP for non spring component
  28. Integration tests for AspectJ
  29. Java Aspect-Oriented Programming with Annotations
  30. how to retransform a class at runtime

Leave a Comment