Return-Path: <mbraden@utenzi.com>
Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list tomcat-dev@jakarta.apache.org
Received: (qmail 4583 invoked from network); 1 Mar 2001 21:50:22 -0000
Received: from office.ilan.net (216.27.3.20)
  by h31.sny.collab.net with SMTP; 1 Mar 2001 21:50:22 -0000
Received: by office.ilan.net with Internet Mail Service (5.5.2650.21)
	id <FQM9163T>; Thu, 1 Mar 2001 16:49:50 -0500
Message-ID: <8940E26B14DA3E489D6E38084542C5740297B0@goldmine.ilan.net>
From: Mike Braden <mbraden@utenzi.com>
To: "'tomcat-dev@jakarta.apache.org'" <tomcat-dev@jakarta.apache.org>
Subject: RE: Tomcat 4 unpacking of WAR files behavior
Date: Thu, 1 Mar 2001 16:49:40 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N


>> If unpackWARs="false", then nothing is expanded out into webapss, the war
>> file is expanded out as needed into the work dir, correct?
>
>The JARs are indeed expanded as a temporary fix for Jasper. There is hope
>that we can perhaps use a tweaked version of javac which would load classes
>from a classloader (in which case no expanding is needed).

Seems to me that running from a war directly would be a problem for
performance
anyway.  Wouldn't you have to unzip them somewhere?  RAM?