When SSM + Maven project is running, it is prompted that org.springframework.web.servlet.dispatcherserservlet cannot be found
When running SSM project today, an error is reported:
HTTP status 500 – error identifying servlet class org. Springframework. Web. Servlet. Dispatcherservlet
java. Lang. classnotfoundexception: org. Springframework. Web. Servlet. Dispatcherservlet
You can confirm that org. Springframework. Web. Servlet. Dispatcherservlet exists and Maven is imported normally
Problem solving method:
select item – & gt; Right click Properties – & gt; Select deployment asset – & gt; Select Add – & gt; Select Java build path entries – & gt; Next-> Select Maven dependencies – & gt; Finish-> Apply-> OK
It can solve the problem
————————————————
Link to the original text: https://blog.csdn.net/cd19930508/article/details/80256595
Read More:
- Error in Maven packaging web project: webxml attribute is required (or pre existing WEB-INF)/ web.xml if executing in update)
- maven_ Unable to create servlet file under Java Web project
- Research on Maven management of Java project pom.xml The jar package error is reported, but the project is running normally
- Spring boot project running error: Servlet.service () for servlet [dispatcherServlet] threw exception
- Org.springframework.beans.factory.xml.xmlbeandefinitionstoreexception: the wildcard matching is comprehensive, but the declaration of element XX: XX XX cannot be found
- The spring boot project was first created, pom.xml The error is Maven configuration problem. How to solve it?
- Maven project running servlet jump JSP error: HTTP status 500 – unable to compile class for JSP
- The import Maven project appears http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException Solutions
- After windows VM is installed successfully, it is always prompted that this application may not work properly
- Idea couldn’t be found org.springframework.context .support
- The web project removal server reports an error, and the web project in eclipse cannot be automatically deployed to Tomcat
- The connection pool of SSM project database cannot be connected. The project can run normally and the database cannot be connected
- Execution repackage of goal org.springframework.boot:spring-boot-maven-plugin:2.4.0:repackage failed
- When a system is deployed on weblogic12.2.1.3, it reports an error “IllegalStateException zip file closed”. When it is deployed on weblogic12.2.1.2, it does not report an error and can be accessed normally.
- Solution in idea java.lang.ClassNotFoundException : org.springframework.web . context.ContextLoaderListener
- Failed to execute goal org.apache.tomcat.maven:tomcat7-maven-plugin:2.2:run (default-cli) on project
- When WebSphere deploys a project, an error is reported: error 500: javax.servlet.ServletException : SRVE0207E: Uncaught initialization
- Error in project operation org.springframework.beans . factory.BeanCreationException : error creating bean with name can be configured by
- Error creating bean with name ‘org.springframework.security.oauth2.config.annotation.web.configurati
- Error in publishing project with Maven in idea. Git directory is not found! Please specify a valid