Spring pointcut designators differences (within vs execution)

java spring spring-aop pointcut
glazaror picture glazaror · Dec 28, 2013 · Viewed 11k times · Source

Please... can anybody explain me what are the differences between using the following spring pointcut designators?

Using "within pointcut designator":

<aop:pointcut expression="within(my.app.dao.impl.*)" id="commonDaoOperation"/>

Using "execution pointcut designator":

<aop:pointcut expression="execution(public * my.app.dao.impl.*.*(..))" id="commonDaoOperation"/>

I am using the second one in my web-projects (and I think it's the most used), the problem i have found with this approach is that it's consuming a lot of memory in the heap...

After analyzing the "heap dump" of the application server with the "eclipse memory analyzer" i have found that my application is consuming 450 MB and the instances of the class "org.springframework.aop.aspectj.AspectJExpressionPointcut" are consuming 30% of those 450MB...

Each instance of AspectJExpressionPointcut occupy 6 MB (approximately) and this is because each instance mantains a cache of matches with instances of java.lang.reflect.Method and surprisingly there are a lot of java methods cached (methods that my pointcut expression doesnt mentions).

After Reading Spring Documentation, I decided to use the first one approach (within pointcut designator) and now each instance of AspectJExpressionPointcut occupy much less memory.

The question is about that... what is the difference in performance between them...

Many thanks in advance...

Answer

Sotirios Delimanolis picture Sotirios Delimanolis · Dec 28, 2013

The Spring documentation explains the difference:

  • execution - for matching method execution join points, this is the primary pointcut designator you will use when working with Spring AOP
  • within - limits matching to join points within certain types (simply the execution of a method declared within a matching type when using Spring AOP)

In other words, execution matches a method and within matches a type.

In this case, your pointcuts are pretty much equivalent. Your within matches any type in the package my.app.dao.impl and your execution matches all the public methods of any type in the package my.app.dao.impl.

However, execution is implemented, I think, with an interceptor for each matched method (a lot of objects), which within only needs one interceptor since it matches the entire type (very little objects).

Related questions

AspectJ expression gives formal unbound in pointcut error

I have within aspectJ the expression: @Pointcut("within(com.param.cpms.dao.impl.ProjectMetaDaoImpl)") public void daoExceptionHandle() { } At Spring 3.0 startup, I am getting the following error : nested exception is java.lang.IllegalArgumentException: error at ::0 formal unbound in pointcut

Read More
Spring AOP pointcut for all methods in a controller

I want to run some code before every method in a Spring (3.2.3) @Controller. I have the following defined but it won't run. I suspect the pointcut expression is incorrect. dispatcher-servlet.xml <aop:aspectj-autoproxy/> <bean class="com.example.…

Read More
Spring AOP - pointcut for every method with an annotation

I am trying to define a pointcut, that would catch every method that is annotated with (i.e.) @CatchThis. This is my own annotation. Moreover, I'd like to have access to the first argument of the method, which will be …

Read More