tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ru...@us.ibm.com
Subject Re: Jikes for JSP compilation is broken
Date Wed, 19 Jan 2000 19:02:26 GMT


Hans Bergsten wrote:
> Maybe it would be better to actually replace the jspCompilerPath init arg
> with a jspCompilerClass arg, and set it to
org.apache.jaspercompiler.JikesJavaCompiler
> when Jikes is used. Compared to the old approach, the jikes binary must
be in
> the PATH, since the absolute path to the binary can no longer be
specified
> with this solution. That should not be a problem though.

The JSPEngine could certainly pass the options to the JavaCompiler it just
created.  The JikesCompiler could easily check to see if there was a
jspCompilerPath specified, and if so, use it.

I'm also inclined to support
   <init-param param-name="jspCompiler" param-value="jikes"/>
 as a shorthand for
   <init-param param-name="jspCompilerClass" param-value="
   org.apache.jasper.compiler.JikesJavaCompiler"/>

With an example or two checked in as comments to the appropriate web.xml
files.

- Sam Ruby



Mime
View raw message