Because dynamic pointcuts consider the parameters of a method in addition to static information such as the name of the method. Because it is dynamic, it is necessary to compute the static information of the method and calculate its parameters, and the result cannot be cached. Therefore, dynamic pointcuts consume more system resources.
The following implementations of dynamic pointcuts are provided in spring, as described below:
1, Controlflowpointcut: Control process entry point. For example, when a connection point is invoked in a particular class or method, the device is triggered, and controlflowpointcut can be used. But its system overhead is very large, in the pursuit of efficient applications, do not recommend the use.
2, Dynamicmethodmatcherpointcut: Dynamic method Matching. is an abstract class that extends the class to implement its own dynamic Pointcut.