In this section, you will learn about Customizing the Default Error Page in Spring MVC.

Customizing the Default  Error Page

In this section, you will learn about Customizing the Default  Error Page in Spring MVC.

When the response body is empty and the response status have error code, generally an well formatted error page in HTML is provide by the Servlet containers. You can customize the default error page of the container by defining an <error-page> element in web.xml.

Prior to Servlet 3.0, you need to provide specific status code or exception type to map with each <error-page> element. After Servlet 3.0, you don' need to map it with specific status code or exception type. Means the page at defined location can be customized.

<error-page>
	<location>/error</location>
</error-page>

Note that the actual location for the error page can be a JSP page or some other URL within the container including one handled through an @Controller method.

The error page can be customize by setting the status code and reason on the error page as follows :

@Controller
public class CustomErrorController {

	@RequestMapping(value="/error", produces="text/html")
	@ResponseBody
	public Map<String, Object> errorHandler(HttpServletRequest request) {
		
		Map<String, Object> errorMap = new HashMap<String, Object>();
		errorMap.put("status", request.getAttribute("javax.servlet.error.status_code"));
		errorMap.put("reason", request.getAttribute("javax.servlet.error.message"));
		
		return errorMap;
	}

}

or in a JSP:

<%@ page contentType="text/html" pageEncoding="UTF-8"%>
{
	status:<%=request.getAttribute("javax.servlet.error.status_code") %>,
	reason:<%=request.getAttribute("javax.servlet.error.message") %>
}

Related Tags for Customizing the Default Error Page:

More Tutorials from this section

• Spring 3.2 Asynchronous Request Processing
• Autogenerated logical view name through RequestToViewNameTranslator
• Chaining of Multiple view resolvers
• ContentNegotiatingViewResolver
• Content Negotiation Configuration
• ControllerClassNameHandlerMapping class for handling convention mapping
• @Controller annotation for defining new controller
• Customizing the Default Error Page
• Customizing the MVC Java config or XML Namespace
• Support for ETag
• @ExceptionHandler & @ResponseStatus annotation
• Spring 3.2
• Interceptors Configuration using Java or XML
• Locales in Spring MVC
• Modification in conventional ModelAndView
• Multipart support for file upload in Spring MVC
• mvc:default-servlet-handler
• MVC Java Config or the MVC XML Namespace
• Processing Sequence of DispatcherServlet
• Redirecting and forwarding to views