Hi,
It's OK to leave it in common/lib. (IMHO it's also fine to have a copy
for each webapp in WEB-INF/lib, but you stated you don't want that).
Yoav Shapira
Millennium Research Informatics
-Original Message-
From: Wangenheim, Marc [mailto:[EMAIL PROTECTED]
Sent: Friday, June 11, 2004
I have seen this happen as well. I'm fine with putting jars in either
the common/lib or the WEB-INF/lib, but how come shared/lib doesn't work
at all? Nothing that gets placed in that directory shows up in the
classloader. Is there something I need to configure to get those jars
to load?
Thanks
=)
-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: Friday, June 11, 2004 9:56 AM
To: Tomcat Users List
Subject: RE: Common/lib works shared/lib doesn't
Hi,
It's OK to leave it in common/lib. (IMHO it's also fine to have a copy
for each webapp in WEB-INF/lib
To: Tomcat Users List
Subject: Re: Common/lib works shared/lib doesn't
I have seen this happen as well. I'm fine with putting jars in either
the common/lib or the WEB-INF/lib, but how come shared/lib doesn't work
at all? Nothing that gets placed in that directory shows up in the
classloader
/lib or not.
Yoav Shapira
Millennium Research Informatics
-Original Message-
From: Charles N. Harvey III [mailto:[EMAIL PROTECTED]
Sent: Friday, June 11, 2004 10:14 AM
To: Tomcat Users List
Subject: Re: Common/lib works shared/lib doesn't
I have seen this happen as well. I'm fine
:[EMAIL PROTECTED]
Sent: 11 June 2004 15:18
To: Tomcat Users List
Subject: RE: Common/lib works shared/lib doesn't
OK I'll leave it in common/lib. The problem with WEB-INF/lib is that is
takes too much time to update all webapps. We have a rather cumbersome
environment. Each app has to go
