0

I'm writing some methods to deal with database operations. Each method first gets a connection, do the operations, and close the connection at end.

I wonder if Spring AOP can help handling the connection acquiring and closing. Specifically I want something like:

@Aspect
@Component
public class ConnAspect {
    @Around("@annotation(connHandle)")
    public void handleConnection(ProceedingJoinPoint pjp, ConnHandle connHandle) throws Throwable {
        Connection conn = datasource.getConnection();
        pjp.proceed(); // can pjp get variable conn?
        conn.close();
    }
}

@Component
public class DbOperation {
    @ConnHandle
    public void operation1(...) {
        ... // do some operation with conn
    }
    ...
}

Is it possible to do so? Or should I turn to other solutions? Thanks for any hints and answers.

Nicolás_Tsu
  • 163
  • 1
  • 2
  • 10
  • 1
    You should be able to leverage [`proceed(Object[] args)`](https://javadoc.io/doc/org.aspectj/aspectjrt/latest/org/aspectj/lang/ProceedingJoinPoint.html#proceed(java.lang.Object%5B%5D)). – sp00m May 16 '22 at 14:59
  • Adding on to @sp00m's suggestion : https://docs.spring.io/spring-framework/docs/current/reference/html/core.html#aop-ataspectj-advice-proceeding-with-the-call – R.G May 17 '22 at 00:26

1 Answers1

1

No, this is not possible, and the suggestions in the comments are not going to help you. You cannot magically inject a non-existent method parameter or local variable into a method. Besides, what you are trying to do is anti AOP: not to encapsulate your cross-cutting concern in an aspect, but somehow bleed aspect context into your application, which ideally should be unaware of the aspect and work without it. You should rather describe what you want to achieve instead of being fixated on a specific (bad) design you have dreamed up to implement your idea.

Besides, there are simpler, reflective ways for a method to fetch its own annotations than to abuse AOP for that purpose.

kriegaex
  • 63,017
  • 15
  • 111
  • 202