On Thu, 19 Jul 2001, David Rees wrote:
> (Sorry about the double-qoute, I missed the original message)
>
>
> I have noticed the same problem while doing some development using
> Tomcat 3.2.[23]. I worked around it by making sure that I unset the
> classpath before calling startup.sh, then things seemed to work properly
> and classes were found as expected.
Tried that. Tried hard-coding the classpath. If the web applications
WEB-INF/classes directory was in the system classpath, it compiles. If it
is not in the system classpath, the JSP's do not compile.
So, why does Jasper not know about the web-application classpath?
Will
