javax.servlet.jsp.JspException cannot be resolved to a typehttps://www.eclipse.org/forums/index.php/mv/msg/204817/655001/#msg_655001
Tomcat 6.0.24
Eclipse Helios 3.6
Java 1.6 (? - Why is the path to the home directory different for 6 than for 5 and previous versions ? )

I have written jsp's that have worked just fine both in previous editions of eclipse as well as in production. I have made changes to the build path, mostly class path changes moving jar files from the web app lib into the lib of the Tomcat install and such.

At the moment I have two JSP errors for my project in Eclipse that I cannot resolve and will not go away. They are :

javax.servlet.jsp.JspException cannot be resolved to a type
javax.servlet.jsp.PageContext cannot be resolved to a type

These two errors are the distinct messages that comprise 36 errors in my build. There are no other.

In an effort to resolve these errors, I've tried :

- refreshing files, folders, and projects
- cleaning the project in question as well as all projects in the workspace
- resetting the JRE directory ( this is problematic in the sense that when I set the path to the home directory of my JDK, it is overridden by eclipse ? )
- deleting and re-importing the project into the workspace.
- confirming that the jar file servlet-api.jar is on the build path of the project.
- unselecting "build automatically" then cleaning the project.
- unselecting jsp syntax validation in the "Configure workspace settings" option of project -> properties -> validation.

Completely at a loss. Seeking help from the forum. Many thanks for any advice and direction.]]>linen 2011-02-17T22:49:26-00:00Re: javax.servlet.jsp.JspException cannot be resolved to a typehttps://www.eclipse.org/forums/index.php/mv/msg/204817/655265/#msg_655265
I can avoid dealing with the error messages by disabling JSP validation at the general properties level.
So I go to "Eclipse" -> "Preferences" -> "Validation" and there I unselect JSP Content Validator and JSP Syntax Validator and I avoid the error messages this way.

I can run the application now.

I've also decided to use Java 5 rather than Java 6.
]]>linen 2011-02-18T21:28:51-00:00