View returned from @ExceptionHandler does not take into account response content type [SPR-7586]

[spring-projects-issues]

Harman opened SPR-7586 and commented

Hi,

I am using Spring Rest to process JSON request and return a JSON response, all works fine.

Now i want to return a html view to user in case JSON request processing throws an exception. For this i have used @ExceptionHandler to create a ModelAndView, but after returning the response DispatcherServlet uses MappingJacksonView to render the response.

Is there a way i can render a HTML Page( in case of error) for request with accept header as application/json

Quote:

@ExceptionHanlder(value=MultipleItemsFoundExceptio n.class
public ModelAndView handleMultipleItemError(MultipleItemsFoundExceptio n e, HttpServletResponse response){
ModelAndView mav = new ModelAndView();
mav.setViewName("detail");
mav.addObject("list",e.getItemList());
response.setContentType("text/html");
return mav;
}

---

Affects: 3.0.2

Reference URL: http://forum.springsource.org/showthread.php?p=320611#post320611

[spring-projects-issues]

Arjen Poutsma commented

Sorry, but I'm quite busy with conference preparations, and I don't have the time to fix this before 3.0.5 (due this Thursday).

[spring-projects-issues]

Arjen Poutsma commented

Added formatting.

[spring-projects-issues]

Arjen Poutsma commented

Is there a way i can render a HTML Page( in case of error) for request with accept header as application/json

The whole point of content negotiation is that you should not ignore the Accept header :), so the answer to this would be "no".

But you can work around the whole content negotiation process by setting a View, rather than a view name. Like so:

@ExceptionHanlder(value=MultipleItemsFoundExceptio n.class
public ModelAndView handleMultipleItemError(MultipleItemsFoundExceptio n e, HttpServletResponse response){
ModelAndView mav = new ModelAndView();
mav.setView(new JstlView("/WEB-INF/jsp/detail.jsp"));
mav.addObject("list",e.getItemList());
return mav;
}

[spring-projects-issues]

Arjen Poutsma commented

Furthermore, even though it might be a good feature to look at the set Content-Type of the response (as you do in the snippet), we simply don't have access to the current HttpServletResponse in the ContentNegotiatingViewResolver (or any view resolver, for that matter); we only have access to the request.