NoClassDefFoundError in JSTL: javax/servlet/jsp/jstl/core/Config error,
When springmvc is used, an error is reported when a request is sent after the project is started.
Type Exception ReportMessage Handler processing failed; nested exception is java.lang.NoClassDefFoundError: javax/servlet/jsp/jstl/core/ConfigDescription The server encountered an unexpected condition that prevented it from fulfilling the request.Exceptionorg.springframework.web.util.NestedServletException: Handler processing failed; nested exception is java.lang.NoClassDefFoundError: javax/servlet/jsp/jstl/core/Config org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:986) org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:897) org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:970) org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:861) javax.servlet.http.HttpServlet.service(HttpServlet.java:635) org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:846) javax.servlet.http.HttpServlet.service(HttpServlet.java:742) org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)Root Causejava.lang.NoClassDefFoundError: javax/servlet/jsp/jstl/core/Config
In the project, I have already imported the JSTLjar package.
In some versions mentioned on the Internet, even if you introduce the jstl1.2 package, the uri still reports an error and the tag cannot be found. Now, we can introduce the standard package. But it is also introduced using maven, and an error is still reported.
Again, I found that the Jar package may conflict, which is a common problem during daily development. Therefore, the Jar package conflicts caused by Maven dependency of jstl are solved.
<dependency> <groupId>javax.servlet.jsp.jstl</groupId> <artifactId>jstl-api</artifactId> <version>1.2</version> <exclusions> <exclusion> <groupId>javax.servlet</groupId> <artifactId>servlet-api</artifactId> </exclusion> <exclusion> <groupId>javax.servlet.jsp</groupId> <artifactId>jsp-api</artifactId> </exclusion> </exclusions> </dependency> <dependency> <groupId>taglibs</groupId> <artifactId>standard</artifactId> <version>1.1.2</version> </dependency>
Unfortunately, the result is still the cruel 500
Then start the debug action. After a long test, an error is reported in DispatherServelt ..
It can be seen that an error occurred while calling modelview. The view cannot be found .. Let's look at the springmvc configuration and use the JSTLView. So we will perform a test and delete this attempt and then we will be able to access it.
But I need this view Parser for internationalization, so I am not convinced and continue to find the reason... Last !!! Finally, we found that the jar package under the lib under the target does not have two newly added jar packages !!!!! Okay, you have been crying ,,
After adding the file, restart it.