Return-Path: Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list commons-user@jakarta.apache.org Received: (qmail 4640 invoked from network); 9 May 2003 16:24:30 -0000 Received: from icarus.apache.org (208.185.179.13) by daedalus.apache.org with SMTP; 9 May 2003 16:24:30 -0000 Received: (qmail 76975 invoked by uid 1059); 9 May 2003 16:24:28 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 9 May 2003 16:24:28 -0000 Date: Fri, 9 May 2003 09:24:28 -0700 (PDT) From: "Craig R. McClanahan" To: Jakarta Commons Users List Subject: RE: [Commons] Component Packaging Options In-Reply-To: <73E71EF16978D51197180002A56022D20743C548@ngmnt4mbx03.uk.capitalone.com> Message-ID: <20030509092247.F73823@icarus.apache.org> References: <73E71EF16978D51197180002A56022D20743C548@ngmnt4mbx03.uk.capitalone.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: localhost 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Fri, 9 May 2003, Hope, Matthew wrote: > > Yes indeed that would be problematic. In the absence of the .net feature of > multiple versions of code co-existing in the same VM I would suggest you > need a special class loader to try and achieve it. > Servlet containers do this for you automatically. Simply put the dependent JARs for a particular webapp in its own "/WEB-INF/lib" directory, and ensure that those JARs are not also visible in a container-provided shared repository (i.e. /shared/lib or /common/lib on Tomcat). Craig McClanahan