That's basically correct. The jar is added to the web application's classloader classpath. The web application's classloader is switched in as the context class during request handling for that context.
Larry > -----Original Message----- > From: Mario Felarca [mailto:[EMAIL PROTECTED]] > Sent: Saturday, May 18, 2002 12:23 PM > To: TomcatUser > Subject: RE: Tomcat 3.3.1 and additionalJars > > > Date: Fri, 17 May 2002 12:30:33 -0400 > > > >Both of those should work. There could be some > >classloader issue involved. Can you provide a test > >case of what you are trying to do? > > > >Cheers, > >Larry > > So the base case I am trying is simply allowing access > to the jdom.jar from my webapps. This is to simply > test that the additionalJars property is working. > > Actually, I just thought of something. The > additionalJars value simply adds to the context > classloader's classpath? It would not affect the other > loaders such as apps and common? > > Is that a correct statement? > > Thanks in advance. > > Mario- > > > > > __________________________________________________ > Do You Yahoo!? > LAUNCH - Your Yahoo! Music Experience > http://launch.yahoo.com > > -- > 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]>
