There is a section in the release notes on JNI classes that are shared by multiple apps. I assume this is what he's talking about.
What it boils down to is that you can't put multiple copies of the same library in each of the webapps, you have to put them in either common/lib or shared/lib. This is a headach for us. On Thu, 2004-10-28 at 17:06, Steve Kirk wrote: > Cancel that - I RTFM'd : each webapp has own classloader. but I'm not sure > now what point you're making re the thread....? You've piqued my interest > on this, I'd be interested if you could clarify please. > > > -----Original Message----- > > From: Steve Kirk [mailto:[EMAIL PROTECTED] > > Sent: Thursday 28 October 2004 21:49 > > To: 'Tomcat Users List' > > Subject: RE: JNDI DataSource GlobalResources problem > > > > > > Benson, I read your post on classloading JNI classloading > > with interest. > > Certainly wasn't well-known to me. > > > > Only one question: "counter-example" to what? i.e. is there > > a configuration > > approach on this thread that makes JNI classloading not work > > for multiple > > webapps? at a guess are you talking about putting the DBCP jars in > > WEB-INF/lib? if so, wouldn't putting them in shared/lib > > instead solve it? > > > > > -----Original Message----- > > > From: Benson Margulies [mailto:[EMAIL PROTECTED] > > > Sent: Thursday 28 October 2004 20:47 > > > To: Tomcat Users List > > > Subject: RE: JNDI DataSource GlobalResources problem > > > > > > > > > I think that JNI is the only counter-example. Forgive me if the > > > following is well know but seen as unimportant to all concerned. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
