MVC handler interceptor

Understand the idea

Register the interceptor through MVC configuration. PreHandle can allow or stop handling; postHandle follows successful handler execution before HTML view rendering; afterCompletion runs after completion for the handled flow. Servlet filters wrap the Servlet chain at another layer. Async and exception paths affect callback execution.

A concrete example

filter before → preHandle → controller
→ postHandle → view → afterCompletion → filter after

In the application

See the independently runnable examples in Stage 30.

A component annotation alone does not register an interceptor for MVC routes.

See it in a working stage

• Stage 30: observe handler execution with an interceptor

Related concepts

• Spring bean
• Dependency injection