Spring MVC: Why do I need to (and how do I?) provide a mapping for a JSP view?

I'm not sure what the difference is, but looking at the equivalent in one of my (working) apps, I use InternalResourceViewResolver instead of UrlBasedViewResolver For example.

I'm not sure what the difference is, but looking at the equivalent in one of my (working) apps, I use InternalResourceViewResolver instead of UrlBasedViewResolver. For example: Also, less likely, my web. Xml has a different pattern (/ instead of /*): dispatcher org.springframework.web.servlet.

DispatcherServlet contextConfigLocation WEB-INF/spring/*.spring. Xml 1 dispatcher / Everything else you have looks pretty much the same.

Thanks for this suggestion; unfortunately I've tried this with no difference in results. It seems like the view is being resolved to the JSP with no issues, but instead of the view being rendered the request is being forwarded to the URL corresponding to the view's JSP page, and at that point instead of it being rendered the request is picked up again by the DispatcherServlet which has no mapping for the URL. – James Adams Nov 4 at 16:15 Hmmm.

Are you doing a redirect? If so, see this question that I asked and had answered. – SingleShot Nov 4 at 16:37 No I am not redirecting anywhere within my code, so I'm not sure where the forward is happening, shortcutting the call to renderMergedOutputModel() which I assumed should be called on the View as part of the ModelAndView returned by the controller method (in this case a JSP page for error messages).

– James Adams Nov 4 at 18:24.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.