Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (herse.apache.org: domain of boris.unckel.mlg@gmx.net
 designates 213.165.64.20 as permitted sender)
Message-ID: <45DAFF80.8090203@gmx.net>
Date: Tue, 20 Feb 2007 15:02:40 +0100
From: Boris Unckel <boris.unckel.mlg@gmx.net>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Classloading scenario
References: <4ac1e6310702200200x505d0d7fo1b97db18ab5372cd@mail.gmail.com>
In-Reply-To: <4ac1e6310702200200x505d0d7fo1b97db18ab5372cd@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hello,

Angel Todorov wrote:
> I have the following scenario: one webapp, which has some jars in its
> private WEB-INF\lib dir, and one common jar which I would like to
> share among several webapps. Hence, I am putting this jar into the
> shared\lib directory of Tomcat. The problem is that this common lib
> references classes which are in jars in the first webapp's WEB\lib
> directory. Therefore, I get NoClassDefFoundErrors when this common jar
> loads and tries to refer classes from the webapp's private lib.
>
> Is it possible to achieve a workaround with tomcat's classloading for
> that custom scenario?
there is no workaround, but a better strategy and best practise:
Put *all* JARs of a webapp into WEB-INF/lib, if there is not
a strong usecase or technical reason to do otherwise (i.E. some JDBC drivers
should be put into common/lib or shared/lib).

Sharing classes causes definitly more problems than it solves.

Regards
Boris


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org