We ended up writing our own ContextInterceptor which looked up servlet named
"jsp" and configured it to use jikes:
public void contextInit(Context ctx)
throws TomcatException
{
if(ctx.getDebug() > 0) {
ctx.log("JikesContextInterceptor - init " + ctx.getPath() + " " +
ctx.getDocBase());
}
ServletWrapper wrapper = ctx.getServletByName("jsp");
if(wrapper != null) {
wrapper.addInitParam("jspCompilerPlugin",
"org.apache.jasper.compiler.JikesJavaCompiler");
}
else {
ctx.log("JikesContextInterceptor - no servlet named \"jsp\": " +
ctx.getPath() + " " + ctx.getDocBase());
}
}
and added this class *after* WebXmlReader loading in server.xml.
Not the cleanest way, but we didn't want to put TomCat specific code in all
our web.xmls.
-arun
> -----Original Message-----
> From: Barbara Nelson [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, December 07, 2000 5:58 PM
> To: '[EMAIL PROTECTED]'
> Subject: Using Jikes with Tomcat 3.2 final
>
>
> Has anyone got Tomcat 3.2 final to use Jikes rather than the
> Sun compiler?
> If so, what did you put in the web.xml file. We had it
> working for Tomcat
> 3.1, but I can't seem to get it to work in Tomcat 3.2. I'll
> start debugging
> it tomorrow, but if someone has already figured it out, that
> would save me
> some time :-)
>
> Barbara Nelson.
>
>
>
>
>
