First, what if I don't want Batik available for all of the webapps on the
Tomcat server.

Secondly, from the "manual"


As mentioned above, the web application class loader diverges from the
default Java 2 delegation model (in accordance with the recommendations in
the Servlet Specification, version 2.3, section 9.6). When a request to load
a class from the web application's WebappX class loader is processed, this
class loader will look in the local repositories first, instead of
delegating before looking. All other class loaders in Tomcat 4 follow the
usual delegation pattern.

Therefore, from the perspective of a web application, class or resource
loading looks in the following repositories, in this order:

/WEB-INF/classes of your web application 
/WEB-INF/lib/*.jar of your web application 
Bootstrap classes of your JVM 
System class loader classses (described above) 


Looks like something to bring up on the Tomcat list.

> -----Original Message-----
> From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 27, 2002 9:39 AM
> Subject: Re: Servlet problems
> > From: Higgins, James
> >
> >
> > That works, but can you provide a reason why that works and placing
> >  it in webapps/fop/WEB-INF/lib doesn't?
> >
> >Flakiness in the Tomcat class loader?
> .0.4-b2/RELEAS

Reply via email to