From: "Chuck Chopp" <[EMAIL PROTECTED]> > I'm still at a loss to explain why this happens on just this one Tomcat > implementation.
I'd be more inclined to blame the JVM than Tomcat. Can you diff the generated index_jsp.java files and see if there are any differences? What about trying to compile the offending index_jsp.java file manually, so you can see all the error messages. You'll have to figure out the classpath, but it's just a .java file, javac should be able to compile it. Maybe something interesting is getting masked by the stack traces. If it really is Tomcat causing the problem, you should be able to replace the version they've provided with a newer one. We do it on HP-UX because HP lags behind providing the latest and greatest Tomcat. It might take some configuration, but it's all Java so it _ought_ to run anywhere. -- Wendy Smoak --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
