Shulou(Shulou.com)06/03 Report--

This article mainly explains "how to use AopContext.currentProxy ()". The content of the explanation is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "how to use AopContext.currentProxy ()".

There is no transaction solution for methods calling each other in the same bean AopContext.

In the same class, non-transactional method An invokes transaction method B, and the transaction expires and must be invoked with AopContext.currentProxy (). Xx () for the transaction to take effect.

Method B is called by A, and the cut-in to method B is invalid, but plus AopContext.currentProxy () creates a proxy class that cuts in before and after the method is called in the proxy class.

The call to method B in proxyA can only enhance A, and the call to B in A uses object .B () instead of $proxy.B (), so the cut-in to B is invalid.

AopContext.currentProxy () uses ThreadLocal to save the proxy object, so

AopContext.currentProxy (). B () can solve the problem.

In different classes, non-transactional method An invokes transaction method B, and the transaction takes effect.

In the same class, transaction method An invokes non-transaction method B, and the transaction is propagating.

Transaction takes effect

In different classes, transaction method An invokes non-transaction method B, and the transaction takes effect.

Thank you for your reading, the above is the content of "how to use AopContext.currentProxy ()", after the study of this article, I believe you have a deeper understanding of how to use AopContext.currentProxy (), and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.