The symptom you describe is easily achievable. The main point is that additionalJars adds jars to multiple webapps the same as if you copied jdom.jar to each WEB-INF/lib. You could try putting jdom.jar in your "test" webapp's WEB-INF/lib, remove the additionalJars, and see if the error still occurs.
I would not be surprised if it did. If a servlet depends on another class that in turn depends on jdom.jar classes, and that class lives below the webapp classloader, then you might see the symptom you describe. The class in the lower classloader can't see the classes in the webapp classloader unless special programming is implemented to make it possible, such as using the thread context classloader. Cheers, Larry > -----Original Message----- > From: Mario Felarca [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, May 21, 2002 4:58 AM > To: [EMAIL PROTECTED] > Subject: RE: Tomcat 3.3.1 and additionalJars > > > >From: Larry Isaacs <[EMAIL PROTECTED]> > > > >After adding the jdom.jar and making the server.xml changes > >you describe, I find that I can compile and display the > >following JSP page: > > Hrmm, ok well I am going to rip everything off the system and > try again. > Perhaps something has been convoluted to the point that it > just is not > working anymore. > > From a clean install, all I should have to do is put my > context classes in > place, add the additionalJars attribute, place the jdom.jar, > and start it > up, right? > > If I am missing anything, please let me know. Hopefully this > time it will > work. :) > > Thanks, > > Mario- > > > -- > To unsubscribe, e-mail: > <mailto:tomcat-user-> [EMAIL PROTECTED]> > For > additional commands, > e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
