Maybe this problem is not a big problem, but it provides a solution to the problem: When you think there will be no problems, it is probably the root cause of the problem
When the login interface confirms to jump to web-inf/view/admin/welcome.jsp, 500 is thrown:
Browser side:
HTTP Status 500 - Could not get RequestDispatcher for [/WEB-INF/view/admin/welcome.jsp/]: Check that the corresponding file exists within your web application archive!
type Exception report
messageCould not get RequestDispatcher for [/WEB-INF/view/admin/welcome.jsp/]: Check that the corresponding file exists within your web application archive!
descriptionThe server encountered an internal error that prevented it from fulfilling this request.
exception
javax.servlet.ServletException: Could not get RequestDispatcher for [/WEB-INF/view/admin/welcome.jsp/]: Check that the corresponding file exists within your web application archive! org.springframework.web.servlet.view.InternalResourceView.renderMergedOutputModel(InternalResourceView.java:191) org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:267) org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1225) org.springframework.web.servlet.DispatcherServlet.processDispatchResult(DispatcherServlet.java:1012)
Service-Terminal:
四月 21, 2018 3:44:48 下午 org.apache.catalina.core.StandardWrapperValve invoke
严重: Servlet.service() for servlet [springMVC] in context with path [/ssms2] threw exception [Could not get RequestDispatcher for [/WEB-INF/view/admin/welcome.jsp/]: Check that the corresponding file exists within your web application archive!] with root cause
javax.servlet.ServletException: Could not get RequestDispatcher for [/WEB-INF/view/admin/welcome.jsp/]: Check that the corresponding file exists within your web application archive!
at org.springframework.web.servlet.view.InternalResourceView.renderMergedOutputModel(InternalResourceView.java:191)
at org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:267)
at org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1225)
at org.springframework.web.servlet.DispatcherServlet.processDispatchResult(DispatcherServlet.java:1012)
at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:959)
at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:876)
at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:961)
at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:863)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:648)
at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:837)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:292)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)
Root of the problem: A configuration error occurred in spring-mvc.xml:
Summary: To view exceptions, you still have to watch them on the console side, not on the browser side. In addition, remember to solve Exceptions. The starting point is console info.