Hi,
I too missed the original message, but have been dealing with these
problems myself.
Have you tried using the Jdk12Interceptor? That fixed class loading
problems for me. In your server.xml do:
<RequestInterceptor
className="org.apache.tomcat.request.Jdk12Interceptor"/>
There are some weird classloader issues w/ Java 2 that this fixes.
Note this will only fix the loading of CLASSES... if you have resources
in your WEB-INF/classes directory, such as .properties files, that the
ClassLoader is supposed to pick up, this will not happen. I submitted a
patch for this to the mailing list last night, but haven't heard
anything from a developer/committer yet.
A good way to see what ClassLoader is being used is by sticking in a
System.out.println( "CL: " +
Thread.currentThread().getContextClassLoader().toString() );
If it says com.sun.misc.something (I forget the package name), you are
using the System classloader... if it says AdaptiveClassLoader, you are
using the Tomcat one which knows about stuff in the WEB-INF directory.
David
Will England wrote:
>
> 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
--
David Haraburda - [EMAIL PROTECTED]
Everest - Helping You Manage Outsourcing
972-980-0013 x736
