Code analysis of spring interceptor handlerinterceptor interface

Spring's handlermapping supports interceptors. Interceptors must implement the handlerinterceptor interface, which contains the following 3 methods:

1. The prehandle() processor is called before execution. The method returns true to indicate that other interceptors or processors will continue to be called. Returning false indicates that the process is interrupted and subsequent interceptors and processors will no longer be executed.

After 2.postHandle () processor executes, it is called before the view is executed. At that time, the data model data is processed or the view is processed through the ModelAndView object.

3.afterCompletion () is called after the whole process is finished, for example, in the performance monitoring, we can record the end time and output the consumption time here, or we can write the cleaning of resources here, but only when preHandle () returns to true will the afterCompletion method be executed.

To implement the handlerinterceptor interface, this custom interceptor needs to implement all the methods in the interface. If you want to use only one method, you can inherit the handlerinterceptoradapter

Interceptor configuration

summary

The above is all about the code analysis of the handlerinterceptor interface of the spring interceptor in this article. I hope it will be helpful to you. Interested friends can continue to refer to other related topics on this site. If there are deficiencies, please leave a message to point out. Thank you for your support!