Ugh, more class loader issues... I dunno why I've never run into these,
aside from JNDI bunk. If it's a class loader problem, you'll have to search
the archive and listen to the ongoing discussions.
- r
> -----Original Message-----
> From: Lund, Kevin [mailto:[EMAIL PROTECTED]]
> Sent: June 13, 2001 9:54 AM
> To: '[EMAIL PROTECTED]'
> Subject: RE: NoClassDefFoundError
>
>
> > I would suggest to look at
> > %TOMCAT_HOME%/logs/jasper.log - it will
> > show you the classpath its using for each request, although
> > it sounds like
> > the jar isn't in the right place - you need to put it into
> > webapp/WEB-INF/lib folder and its name must end in .jar.
>
> Well, it's in the right place, it has the right name, and it
> is listed in
> the jasper.log entry. [sigh] My web app specifies a class
> loader servlet to
> run at startup, which is also in this jar file, and gets
> executed without a
> problem. After that, however, any class in this jar file gets a
> NoClassDefFoundError. I'm sure there is a simple answer (I
> just wish it was
> as simple as not having the jar file in the right location).
>
> Thanks,
> Kevin
>
