[justjavi]

Yeah, I do… And I was actually going to do that within the next day or two so I can update our development environment install instructions. I probably won’t get to that until this afternoon at the earliest though.

[Riyad Kalla]

Justin,
I should have clarified that we need JSP pages we can compile to try and simluate your setup… can you create alittle sample project that exhibits this problem, then use File > Export > ZIP and send us the Zip file? I want to try and reproduce what you are seeing…

[justjavi]

Yeah, I was afraid of that… Our system is fairly large, and I’m not sure how easily I can bite off a chunk and send it off… I’ll see what I can do…

[justjavi]

I’m not sure if this means anything, but I was just checking the .log file and the messages that had been showing up for every jsp (that I had posted before) don’t show up anymore. There’s nothing in that file now when I do clean builds. The errors remain though…

[Riyad Kalla]

…. strange. And it occurs for every JSP page correct?

[justjavi]

Yes, the error shows up for every jsp. Although I’ve noticed now that it does not show up if there is another error in the jsp (such as a link to an included file that doesn’t exist). It seems to only show up when there are no other errors (excluding HTML validation errors).

[justjavi]

I’m gonna take a stab in the dark and guess that uninstalling the old Java SDK had something to do with those messages in the log disappearing… Not that I’m an expert on Eclipse log messages…

[James M. Miller]

Im getting the same error. Has this been resolved yet???

[Geoff The]

Same error here. Any progress or hints on resolving this issue?

[Riyad Kalla]

Guys sorry about the silence on this thread, I wasn’t getting notified of replies to it, but now I am.

Can the people still having trouble exactly state the issue (basically tell me how to reproduce it locally), saying “I have the same problem” rarely ends up being the case and there is sometimes a slight variation that provides me enough info to trouble shoot it differently.

[Geoff The]

Actually, after reading through a number of the other replies to similar problems, I figured out that my problem was related to the fact that my project has a version of the jasper-runtime.jar in its CLASSPATH that preceeded the myeclipse version. From the .log:

!ENTRY com.genuitec.eclipse.wdt.jsp.debug 1 1 Mar 02, 2005 10:50:19.504

!MESSAGE classpath=C:\bin32\j2sdk1.4.2_06\jre\lib\rt.jar;C:\bin32\j2sdk1.4.2_06\jre\lib\sunrsasign.jar;C:\bin32\j2sdk1.4.2_06\jre\lib\jsse.jar;C:\bin32\j2sdk1.4.2_06\jre\lib\jce.jar;C:\bin32\j2sdk1.4.2_06\jre\lib\charsets.jar;C:\bin32\j2sdk1.4.2_06\jre\lib\ext\dnsns.jar;C:\bin32\j2sdk1.4.2_06\jre\lib\ext\ldapsec.jar;C:\bin32\j2sdk1.4.2_06\jre\lib\ext\localedata.jar;C:\bin32\j2sdk1.4.2_06\jre\lib\ext\sunjce_provider.jar;c:\src\myeclipse\MyProject\WEB-INF\lib\commons-collections-3.0.jar;c:\src\myeclipse\MyProject\WEB-INF\lib\commons-dbcp-1.1.jar;c:\src\myeclipse\MyProject\WEB-INF\lib\commons-fileupload-1.0.jar;c:\src\myeclipse\MyProject\WEB-INF\lib\commons-pool-1.1.jar;c:\src\myeclipse\MyProject\WEB-INF\lib\mailapi.jar;c:\src\myeclipse\MyProject\WEB-INF\lib\smtp.jar;C:\bin32\junit3.8.1\junit.jar;C:\bin32\jakarta-tomcat-4.1.31\common\lib\activation.jar;C:\bin32\jakarta-tomcat-4.1.31\common\lib\jasper-runtime.jar;C:\bin32\jakarta-tomcat-4.1.31\common\lib\servlet.jar;C:\bin32\jakarta-tomcat-4.1.31\shared\lib\msbase.jar;C:\bin32\jakarta-tomcat-4.1.31\shared\lib\mssqlserver.jar;C:\bin32\jakarta-tomcat-4.1.31\shared\lib\msutil.jar;c:\src\myeclipse\JavaCommLib\dist\entact_jcl_1.1_04237.jar;c:\src\myeclipse\MyProject\WEB-INF\lib\axis.jar;c:\src\myeclipse\MyProject\WEB-INF\lib\axis-ant.jar;c:\src\myeclipse\MyProject\WEB-INF\lib\commons-discovery.jar;c:\src\myeclipse\MyProject\WEB-INF\lib\commons-logging.jar;c:\src\myeclipse\MyProject\WEB-INF\lib\jaxrpc.jar;c:\src\myeclipse\MyProject\WEB-INF\lib\jstl.jar;c:\src\myeclipse\MyProject\WEB-INF\lib\log4j-1.2.8.jar;c:\src\myeclipse\MyProject\WEB-INF\lib\saaj.jar;c:\src\myeclipse\MyProject\WEB-INF\lib\standard.jar;c:\src\myeclipse\MyProject\WEB-INF\lib\wsdl4j.jar;c:\src\myeclipse\MyProject\WEB-INF\classes;d:\bin32\MyEclipse\eclipse\plugins\com.genuitec.eclipse.wdt.jsp.debug_3.8.4\lib\jasper-runtime.jar;d:\bin32\MyEclipse\eclipse\plugins\com.genuitec.eclipse.wdt.jsp.debug_3.8.4\lib\jsp-api.jar

Removing the project-reference to the jasper-runtime.jar seems to have resolved my problem. Thanks for the reply!

[Riyad Kalla]

That is a really tricky one, we have an issue to track our classloader use to try and avoid situations like this in the future. Thanks for running that down yourself.

[Author]

Posts