On Wed, 15 Nov 2000, Brian Bucknam wrote:
> On a separate topic, we're having some classloader problems
> where classes supposedly available in .jars in WEB-INF/lib come
> up as "NoClassDefFound" as supporting classes for some servlets
> and JSP pages. Moving these jars to jakarta-tomcat/lib solves
> the problem. I haven't had time to track down exactly where the
> problem is, but it seems wrong that the web-app classloader that
> loads the servlets & JSP's seems to be ignoring the lib jars,
> or acting as if the classes in those jars came from a different
> loader. I probably should get better details before bringing
> this to the list, but I saw Rickard Öberg's mention of a
> getResource() problem...
>
> My $.02,
> Brian
Regarding Tomcat 3.1
I've been talking to people at work who also use Tomcat and we've all come
to the conclusion that the classloader for each context mapping is:
A) Strange
B) Slow
C) To be avoided
In other words, when in doubt, we end up sticking the classes and jars in
Tomcat's classpath, (even the WEB-INF/classes directory!) and giving up on
servlet reloading.
Hopefully Tomcat 3.2 isn't as bad.
