Written yesterday about the solution Javaweb: Error message the superclass "Javax.servlet.http.HttpServlet" was not found on the Java scheme very good to overcome this error, But it doesn't completely solve my problem, and the MAVEN project still has a red exclamation mark. The reason the red exclamation mark exists is that the. Classpath configuration file references a jar package, but the jar does not exist in Lib. The problem that I encountered is a new situation, jar exists in Lib, but still report two errors in the topic. Detailed research found my JAVAEE-API this jar package, although it exists in the local MAVEN library, is the wrong jar (found to be easy to find because it is empty). Solutions such as the following: first to remove the project Maven dependency error Javaee-api.jar (in the Pom file to remove the jar's dependency configuration and then save the jar from the project's Maven dependency), and then to the MAVEN local library to remove the error, and then to the Pom file to the jar dependencies to configure the Save it and you can bring the right jar into the project, and the problem is overcome.
MAVEN Project Red exclamation mark +javaweb: Error message the superclass "javax.servlet.http.HttpServlet" Was wasn't found on the Java B
