And for some twisted reason, I won't use WEB-INF/lib.
That is twisted!
Rui
On Tue, 25 May 2004, Rui Zhang wrote:
> Well, I tired both. Neither worked... >
What are you trying? I have certain jars in shared/lib and it works fine for me. The jars I put in shared/lib are the jars with javax.* stuff in them. These shoudn't been in WEB-INF/lib anyway. They should be treated as if they are part of the JDK and, as such, endorsed.
More below....
> Rui > > On Tue, 25 May 2004, Joe Nall wrote: > > > > > On May 25, 2004, at 5:41 PM, Jacob Kjome wrote: > > > > > At 10:16 PM 5/25/2004 +0100, you wrote: > > >> Hi all, > > >> > > >> Is it possible to configure Axis to load the classes resided in > > >> Tomcat > > >> (say, in /server/classes)? > > > > > > No, that is for Tomcat's internal use only and is hidden to all other > > > classloaders. Try using common/lib or shared/lib (only if you can't > > > or won't use WEB-INF/lib). > > > > What is the logic for determining if a library should go in shared/lib > > or common/lib? > >
shared/lib is separate among CATALINA_BASE instances. That is, if you have multiple instances of Tomcat running with different CATALINA_BASE paths, shared/lib with be separate between them (each will have their own). common/lib, on the other hand, is shared between all Tomcat instances. It is also where you should put jars that the container needs to see such as JDBC drivers if you are using container managed datasources. The server can't see stuff in shared/lib. If the server doesn't need to see it, but your apps do, put jars in shared/lib. If both your apps and the server need to see the jars, put them in common/lib. However, put as much as you can in WEB-INF/lib and avoid a whole host of classloading oddities.
Jake
> > joe > > >
