Try adding JAVA_HOME/bin to your PATH. Extend JAVA_HOME to its actual value before adding it to your PATH.
John
On 11 Jun 2003 10:56:56 -0400, Jeff Self <[EMAIL PROTECTED]> wrote:
On Tue, 2003-06-10 at 08:25, [EMAIL PROTECTED] wrote:Hi All,
I just upgraded my production box to Tomcat 4.1.24 and j2SE1.4_02 from TC4.1.18 and J2SE1.3_x, and now my JSP's are failing:
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(DefaultErrorHandle
r.java:130)
at
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:2
93)
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:4
73)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:1
90)
The funny thing is I performed the same steps first on my test box, upgrading to 4.1.24 and J2SE1.4_02 there, and everything works.
I can't seem to figure out if this is an ant issue or what... Any pointers
would be much appreciated...
Eric
I'm getting the same thing. I just upgraded to Tomcat 4.1.24 from 4.1.18 on Debian and its happening here. I submitted a bug report to Debian thinking it was a problem with the packaging.
My servlets are working but the JSP's are failing.
-- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
