[slackorama]

Getting a weird error from the jsp compiler:

org.apache.jsp.cache_005fcheck_jsp is not abstract and does not override abstract method getIncludes() in org.apache.jasper.runtime.HttpJspBase: public final class cache_005fcheck_jsp extends org.apache.jasper.runtime.HttpJspBase. NOTE: No JSP line number was avaliable so line 1 was used for the marker.

I’ve got the same project installed on a different machine running the same versions of eclipse and myeclipse but it doesn’t have these errors.

Any ideas? Thanks in advance for any help,

SETH

config summary below:
*** Date: Wed May 17 17:50:21 PDT 2006

*** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.5.0_06

*** MyEclipse details:
MyEclipse Enterprise Workbench

Version: 4.1.1 GA
Build id: 20060228-4.1.1-GA

*** Eclipse details:
Eclipse SDK

Version: 3.1.2
Build id: M20060118-1600

Eclipse Platform

Version: 3.1.2
Build id: M20060118-1600

Eclipse RCP

Version: 3.1.2
Build id: M20060118-1600

Eclipse Java Development Tools

Version: 3.1.2
Build id: M20060118-1600

Eclipse Plug-in Development Environment

Version: 3.1.2
Build id: M20060118-1600

Eclipse Project SDK

Version: 3.1.2
Build id: M20060118-1600

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-launcher
C:\installs\eclipse\eclipse-SDK-3.1.2-win32\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
1bc_60
-vm
C:\jdk\bin\javaw.exe

[Riyad Kalla]

Do you have any Jasper libraries on your project’s build path? Also if you check your JRE /ext dir for 3rd party libraries for the JRE that is used to run MyEclipse, do you see any?

[slackorama]

I had the jasper runtime and compiler jars in my build path. Removing those fixed the problem. Thanks!

Just for my own curiousity (and if it’s not too much trouble), can I get an explanation as to why?

thanks again,
SETH

[Riyad Kalla]

SETH,
We looked into class loader issues in the past thinking that for some reason our plugin class loader is getting poluted by the project classpath and weren’t able to find much, but it looks like we still have a poluted classloader issue where your project’s classpath is actually effecting the classloader used to run the JSP validation.

This should all be fixed in MyEclipse 5.0 as we have gone back to a JDT/WTP-based JSP validator/builder step. No more Jasper.

[Author]

Posts