Skip to main content

Spring MVC Handler Interceptor example

Spring MVC allow you to intercept web request through handler interceptors. The handler interceptor have to implement the HandlerInterceptor interface, which contains three methods :
  1. preHandle() – Called before the handler execution, returns a boolean value, “true” : continue the handler execution chain; “false”, stop the execution chain and return it.
  2. postHandle() – Called after the handler execution, allow manipulate the ModelAndView object before render it to view page.
  3. afterCompletion() – Called after the complete request has finished. Seldom use, cant find any use case.
In this tutorial, you will create one handler interceptor to show the use of the HandlerInterceptor.
MaintenanceInterceptor – Intercept the web request, check if the current time is in between the maintenance time, if yes then redirect it to maintenance page.
It’s recommended to extend the HandlerInterceptorAdapter for the convenient default implementations.
Intercept before the controller execution, check if the current time is in between the maintenance time, if yes then redirect it to maintenance page; else continue the execution chain.
File :
import java.util.Calendar;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import org.springframework.web.servlet.handler.HandlerInterceptorAdapter;
public class MaintenanceInterceptor extends HandlerInterceptorAdapter{
 private int maintenanceStartTime;
 private int maintenanceEndTime;
 private String maintenanceMapping;
 public void setMaintenanceMapping(String maintenanceMapping) {
  this.maintenanceMapping = maintenanceMapping;
 public void setMaintenanceStartTime(int maintenanceStartTime) {
  this.maintenanceStartTime = maintenanceStartTime;
 public void setMaintenanceEndTime(int maintenanceEndTime) {
  this.maintenanceEndTime = maintenanceEndTime;
 //before the actual handler will be executed
 public boolean preHandle(HttpServletRequest request, 
   HttpServletResponse response, Object handler)
     throws Exception {
  Calendar cal = Calendar.getInstance();
  int hour = cal.get(cal.HOUR_OF_DAY);
  if (hour >= maintenanceStartTime && hour <= maintenanceEndTime) {
   //maintenance time, send to maintenance page
   return false;
  } else {
   return true;

Enable the handler interceptor

To enable it, put your handler interceptor class in the handler mapping “interceptors” property.
<beans xmlns=""
 <bean class="org.springframework.web.servlet.handler.SimpleUrlHandlerMapping">
  <property name="mappings">
    <prop key="/welcome.htm">welcomeController</prop>
  <property name="interceptors">
    <ref bean="maintenanceInterceptor" />
 <bean id="welcomeController" 
                  class="com.mkyong.common.controller.WelcomeController" />
 <bean class="com.mkyong.common.controller.MaintenanceController" />

 <bean id="maintenanceInterceptor" 
  <property name="maintenanceStartTime" value="23" />
  <property name="maintenanceEndTime" value="24" />
  <property name="maintenanceMapping" value="/SpringMVC/maintenance.htm" />
 <bean id="viewResolver"
  <property name="prefix">
  <property name="suffix">


Popular posts from this blog

Stretch a row if data overflows in jasper reports

It is very common that some columns of the report need to stretch to show all the content in that column. But  if you just specify the property " stretch with overflow' to that column(we called text field in jasper report world) , it will just stretch that column and won't change other columns, so the row could be ridiculous. Haven't find the solution from internet yet. So I just review the properties in iReport one by one and find two useful properties(the bold highlighted in example below) which resolve the problems.   example:
<band height="20" splitType="Stretch"> <textField isStretchWithOverflow="true" pattern="" isBlankWhenNull="true"> <reportElement stretchType="RelativeToTallestObject" mode="Opaque" x="192" y="0" width="183" height="20"/> <box leftPadding="2"> <pen lineWidth="0.25"/> …

JasperReports - Configuration Reference

Live - solving the jasper report out of memory and high cpu usage problems

I still can not find the solution. So I summary all the things and tell my boss about it. If any one knows the solution, please let me know.

Symptom: 1.The JVM became Out of memory when creating big consumption report 2.Those JRTemplateElement-instances is still there occupied even if I logged out the system
Reason:         1. There is a large number of JRTemplateElement-instances cached in the memory 2.The clearobjects() method in ReportThread class has not been triggered when logging out
Action I tried:      About the Virtualizer: 1.Replacing the JRSwapFileVirtualizer with JRFileVirtualizer 2.Not use any FileVirtualizer for cache the report in the hard disk Result: The japserreport still creating the a large number of JRTemplateElement-instances in the memory     About the work around below,      I tried: item 3(in below work around list) – result: it helps to reduce  the size of the JRTemplateElement Object                Item 4,5 – result : it helps a lot to reduce the number of  JRTemplateE…