-
1. Re: JSP deployment error running
jonlee Oct 21, 2003 2:33 AM (in response to sasconsul)The classpath is definitely too long. Try setting Jasper to compile the JSP internally - that is not to fork. You will need to add it to server/default/deploy/jbossweb-jetty.sar/webdefault.xml for Jetty or server/default/deploy/jbossweb-tomcat41.sar/web.xml for Tomcat. This applies to the Jasper section of the aforementioned configuration files.
<servlet-name>jsp</servlet-name>
<servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
<!-- add this -->
<init-param>
<param-name>fork</param-name>
<param-value>false</param-value>
</init-param>
More information here:
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jasper-howto.html
This should stop the system having to pass the classpath externally, which is where the problem is occurring. The drawback is that there is a chance of a crash if there is a memory leak in javac. Shouldn't be the case for Java JDK 1.4.2 but YMMV.
Hope it helps.