Eclipse Ganymede not validating JSPs properly

Question

I just installed Ganymede and am exploring an old project in it. All of my JSPs are giving me weird validation errors. I'm seeing stuff like -

Syntax error on token "}", delete this token
Syntax error on token "catch", Identifier expected
Syntax error, insert "Finally" to complete TryStatement

I'm doing best practice stuff here, no scriplets or anything, so I think that Eclipse is incorrectly applying a Java class validator to my JSPs. Any idea on how to stop that from happening?

Under Options/Editors/File Associations I have the following for JSPs:

JSP Editor (default)
Web Page Editor
Text Editor
CSS JSP Editor

Am I missing something?

Also I think this is correct, but just in case it's not, here is my page directive -

<%@ page language="java" contentType="text/html; charset=ISO-8859-1"
pageEncoding="ISO-8859-1"%>

Actinomorphic

I gave up on Ganymede because I couldn't find a way to turn off its validation. The errors you're seeing are from the Java code that Eclipse is generating from your JSP. It may be generating the wrong code because of a bug in your JSP, but if it can't identify the problem, what good is it? – Couch

Answer 1

I have just downloaded Ganymede 3.4.2 and added WTP 3.0.4 to it and this error has gone for me.

Ringe

Answer 2

I actually found out what my problem was through the eclipse webtools usergroup. The issue for me was the use of the Spring form custom tag library. If you self-close the tag...

<form:errors path="*" />

...then you get the goofy JSP validation error. If you close the tag as if there was body content...

<form:errors path="*"></form:errors>

Then the error goes away. I need to follow-up with a bug for the Ganymede team.

Zimmermann

Answer 3

It's not actually something about the editor itself.

This usually happens because of
A) custom tags that are missing a start or end tag cause an imbalance in the translation
or
B) is the result improper handling of scripting variable for custom tags by the JSP Validator.

One's a fault in the JSP file and the other's the fault of the validator. Neither will cause this problem in the upcoming WTP 3.0.3 and Ganymede SR2 releases.

Function

Answer 4

I just ran a update for Software Updates->Gynemede Update Site-> "Web and Java EE Development" and the error seems to go away.

Ensheathe

There's still a lot to go: bugs.eclipse.org/bugs/buglist.cgi?quicksearch=jsp – Borkowski

Answer 5

Under preferences -> editors -> file associations, you can see which editor(s) are associated with .jsp files. Perhaps it got associated with a wrong editor, and content checking. You can find a reasonably good JSP editor in the Web Tools Platform (WTP) toolkit.

Marigolde

Answer 6

I have the same issue. Whatever JSP editor is in Ganymede does not like my if/else scriptlets:

<%  if(message != null) { %>
    <p id="message"><%=message %></p>
<%  } else { %>
    <p>Please login to view your account information.</p>
<%  } %>

It tells me:

Syntax error on token "}", delete this token
Syntax error on token "catch", Identifier expected
Syntax error, insert "Finally" to complete TryStatement

...on the final closing brace. I have the same file associations as the original poster. I suppose I will try to find another JSP editor in the WTP toolkit, but I was under the impression that came with my build.

Zimmermann

Answer 7

This is unfortunately a known bug apparently introduced in Service Release 1 of Ganymede (Eclipse Ganymede SR1, v 3.4.1).

See the following pages for more information:

http://www.coderanch.com/t/106846/IDEs-Version-Control-other-tools/Ganymede-bug-using-jsp-include

http://www.eclipse.org/newsportal/article.php?id=17447&group=eclipse.webtools#17447

The bug is fixed in WTP 3.0.3. Note that to get the fix through the Eclipse "Software Updates" function, you have to manually add the WTP update site to the list of sites that get searched during updates, by using the "Maage Sites..." function and check the Eclipse Webtools site.

Margetmargette

Answer 8

Hm, I upgraded to 3.0.3, to no effect. This is happening mostly for <%@ include file="somefile.jsp" %> -style includes. Incredibly frustrating -- makes it very hard to find real errors when I have 300+ of these. Anyone have any luck going back to an earlier version of WTP?

Refuel