[B.Kaatz]

Well, I am not sure where exactly the problem lies in this case, but when I loaded my existing projects from Git into MyEclipse2017CI, I am getting a number of JSP Validation errors that I did not get from MyEclipse2015CI.

Errors are things like “Syntax error on token “)”, try expected after this token” for the last closing paren of the ‘if’ in following block of code:

if((dopreselect.equals("yes"))&&(preyear.equals(years[i]))){
				%>
				<OPTION SELECTED="selected" VALUE="<%= chkyears[i] %>" <%= sel %>><%= years[i] %>
				<%
			} else {
				%>
				<OPTION VALUE="<%= chkyears[i] %>" <%= sel %>><%= years[i] %>
				<%
			}

Now, from the digging I have done on the Eclipse website, it seems there may be an issue with the JSP Validation from WTP within Eclipse. So, how does one go about resolving this?

TIA for the assistance.

[support-swapna]

B.Kaatz,

Sorry that you are seeing this issue. I could replicate the problem at my end. A bug is filed for the dev team to work on it. We will keep you posted about the fix.

Apologies for inconvenience caused.

–Swapna
MyEclipse Support

[Brian Fernandes]

I wanted to add a quick follow up to Swapna’s response. We’re going to prioritize this fix for the 2017 CI 10 release, CI 9 is due in a few days and it’s unfortunately a bit too late to put the fix in.

If you happen to have the Eclipse bugs covering this issue handy, could you please pass them our way?

Again, I realize how frustrating errors like this can be – apologies.

[B.Kaatz]

Greetings and thank you both for your replies and attention to this matter.

For examples of the same and/or similar problems with WTP validation in Eclipse, I found the following bug reports on https://bugs.eclipse.org/:

Bug 365197 – [validation] JSP+EL+JS: Syntax error, insert “}” to complete Block ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=365197 )
Bug 527010 – EL inside HTML attributes is not parsed correctly ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=527010 )
Bug 391342 – JSP Validation can’t see variables from fragments when they are defined within a <script> element ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=391342 )
Bug 466359 – HTML5 <label> element nested inside “a” (READ: “anchor”) element is invalid and the editor should validate it ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=466359 )

So those are just a few of the bugs that come up for “JSP Validation” on Eclipse’s Bugzilla, and going through the StackExchange boards paints a picture that seems to be even worse with regards to WTP. So much so that many of the users on the StackExchange forums are looking at other plugins for JSP validation to bypass WTP’s JSP validation. (e.g. From the following page https://stackoverflow.com/questions/211841/is-there-a-good-jsp-editor-for-eclipse which, BTW, also gives a nod to MyEclipse for surpassing Eclipse’s capability for the same thing back in 2008.)

So, I look forward to hearing from you soon and hope for a speedy resolution.

Thanks again.

• This reply was modified 7 years ago by B.Kaatz. Reason: Readjusting bug title to reflect properly
• This reply was modified 7 years ago by B.Kaatz.

[Brian Fernandes]

I was asking about the Eclipse bugs in case you had located one that corresponded exactly to the issue you were facing – thanks for the list.

We do the JSP validation differently from Eclipse, which is why we are typically free from such issues, and in a much better state than Eclipse – unfortunately this case seems to have slipped through.

We will keep this issue at high priority for the CI 10 release and I will let you know when a fix is available. Thanks!

[B.Kaatz]

Greetings again,

Well, I see that the fix didn’t make it into CI 10, as I have just finally got the update to get installed and still have all the errors.

Any info as to when the fix might be available?

Thanks again.

[support-swapna]

B.Kaatz,

Sorry that the fix did not make it to CI 10. The dev team will get back to you soon about the fix schedule. Thank you for your patience.

–Swapna
MyEclipse Support

[support-tony]

This issue has been fixed in the new 2018 release of MyEclipse. To get the fix, you’ll need to install and use this release (you don’t need a new license for this release). You can use your existing workspace though you may be prompted to migrate it the first time you run the new release. An installer can be downloaded from this page.

[Author]

Posts