[news.eclipse.tools] JSP compilation in Tomcat, started from Eclipse

[thierry.vanacker@xxxxxx (Thierry)]

Hello,

I'm new to this ng and ng's in general, sorry if i'm asking a silly
question.

I'm a user of the sysdeo plugin for Eclipse.

I have the latest version of the sysdeo plugin (2.1).
I'm running on a tomcat 4.1.24 (with the jasperDebug Patch installed).
The eclipse version is 2.1.0.

I'm having the following problem : 

When I put a very simple "hello world" JSP in a Tomcat Project of Eclipse,
I can compile it correctly, but I can't load
it when the Tomcat is started from within Eclipse.

I can fully use my JSP when I start the same Tomcat from outside Eclipse
(with the startup.bat file that came with the Tomcat
installation).

I have tried almost everything to get this to work, but I didn't succeed
so far.
I have also checked the manual procedure, described on the sysdeo site
under "noTomcatProject".
I have double checked : everything is in the correct place, the directory
work and org.apache.jsp do exist.
The jsp does certainly not contain any faults, but it still won't load
when Tomcat is started from Eclipse.

When I start Tomcat via the startup.bat script, I can successful compile
my JSP and use it in a browser.
When I then shutdown Tomcat and start it from within Eclipse, everything
works fine, note that no compilation of JSP is
needed now, since it was already compiled by the script-started Tomcat. 
When I then alter the JSP (recompile is needed now) I am encountering the
same errors.
The JSP does get correctly recompiled, and does appear in Eclipse after a
refresh. But it can't be loaded.
The browser gives me this error : 

HTTP Status 500 - 

--------------------------------------------------------------------------------

type Exception report

message 

description The server encountered an internal error () that prevented it
from fulfilling this request.

exception 

org.apache.jasper.JasperException: Unable to compile class for JSP

An error occurred at line: -1 in the jsp file: null

Generated servlet error:
    [javac] Since fork is true, ignoring compiler setting.
    [javac] Compiling 1 source file
    [javac] Since fork is true, ignoring compiler setting.



	at
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:130)
	at
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:293)
	at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:353)
	at org.apache.jasper.compiler.Compiler.compile(Compiler.java:370)
	at
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:508)
	at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:190)
	at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
	at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
	at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
	at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
	at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
	at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
	at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
	at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
	at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
	at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
	at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
	at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
	at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
	at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
	at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
	at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
	at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
	at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
	at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
	at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
	at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
	at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
	at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
	at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
	at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
	at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
	at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594)
	at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392)
	at
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
	at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
	at java.lang.Thread.run(Thread.java:536)



--------------------------------------------------------------------------------

Apache Tomcat/4.1.24

This is very weird because I can see that the JSP IS CORRECTLY RECOMPILED !
I would like to know what is the problem here and how I can fix it or work
around it.

It has probably something to do with the classpath used when loading or
the way Tomcat is started...

Thanx for any response that could help,

Thierry.