Workaround for accessing the JSP report HTTP Status 500-java.lang.nullpointerexception

When developing the web with eclipse, because there is no servlet and JSP jar package, the development work cannot be done smoothly, and when the jar package is put into the WebApps Lib directory, The jar package for the servlet and JSP in the project conflicts with the JSP and servlet packages in Tomcat, resulting in access to any JSP page that will be reported as "HTTP Status 500-java.lang.nullpointerexception" The error

Workaround: In a MAVEN Web project (or Web project built through Eclipse), do not add a dependency to the servlet and JSP in the Pom file, or put the servlet and JSP jar packages in the WebApps lib directory.

The correct approach is to create a Lib folder at the root of the project, to temporarily store the jar package, and then add the jar package from the project root in the Lib folder in the project's Classpath, which is only temporary for development, When the project is published it is not published to the Lib directory under WebApps, and all does not cause a conflict.

This article from "Small Fish Blog" blog, declined reprint!

Workaround for accessing the JSP report HTTP Status 500-java.lang.nullpointerexception