Return-Path: 
 <tomcat-user-return-53992-qmlist-jakarta-archive-tomcat-user=nagoya.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org
Received: (qmail 40855 invoked from network); 18 Feb 2003 22:36:36 -0000
Received: from exchange.sun.com (192.18.33.10)
  by daedalus.apache.org with SMTP; 18 Feb 2003 22:36:36 -0000
Received: (qmail 23358 invoked by uid 97); 18 Feb 2003 22:38:14 -0000
Delivered-To: qmlist-jakarta-archive-tomcat-user@nagoya.betaversion.org
Received: (qmail 23351 invoked from network); 18 Feb 2003 22:38:14 -0000
Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12)
  by nagoya.betaversion.org with SMTP; 18 Feb 2003 22:38:14 -0000
Received: (qmail 39391 invoked by uid 500); 18 Feb 2003 22:36:18 -0000
Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:tomcat-user-subscribe@jakarta.apache.org>
List-Help: <mailto:tomcat-user-help@jakarta.apache.org>
List-Post: <mailto:tomcat-user@jakarta.apache.org>
List-Id: "Tomcat Users List" <tomcat-user.jakarta.apache.org>
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Delivered-To: mailing list tomcat-user@jakarta.apache.org
Received: (qmail 39380 invoked from network); 18 Feb 2003 22:36:18 -0000
Received: from post2.inre.asu.edu (129.219.110.73)
  by daedalus.apache.org with SMTP; 18 Feb 2003 22:36:18 -0000
Received: from conversion.post2.inre.asu.edu by asu.edu (PMDF V6.1 #40111)
 id <0HAJ00I010305Q@asu.edu> for tomcat-user@jakarta.apache.org; Tue,
 18 Feb 2003 15:35:24 -0700 (MST)
Received: from mainexzz.asu.edu (mainexzz.asu.edu [129.219.10.209])
 by asu.edu (PMDF V6.1 #40111) with ESMTP id <0HAJ00FIP030G8@asu.edu> for
 tomcat-user@jakarta.apache.org; Tue, 18 Feb 2003 15:35:24 -0700 (MST)
Received: by mainexzz.asu.edu with Internet Mail Service (5.5.2653.19)
	id <DSYC348J>; Tue, 18 Feb 2003 15:35:24 -0700
Content-return: allowed
Date: Tue, 18 Feb 2003 15:35:14 -0700
From: Wendy Smoak <Wendy.Smoak@asu.edu>
Subject: RE: 4.1.18 won't unpack my .war file
To: 'Tomcat Users List' <tomcat-user@jakarta.apache.org>
Message-id: <A7AF1AE70A8C124593A1AC831EFE46FE0D6603@ex3.asurite.ad.asu.edu>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_qalw98rRXWYo/gglMPKG7A)"
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

--Boundary_(ID_qalw98rRXWYo/gglMPKG7A)
Content-type: text/plain;	charset="iso-8859-1"

> From what you have described, it is not the WAR file itself that is the
> problem.  It is a configuration problem with naming the WAR or deploying
the
> web application.
> What does your build.properties (or build.xml) file define ${context} to
be?
> (Remember that case matter here.)

It used to say:  
  <property name="context" value="bendev" />

I changed it to
  <property name="context" value="benefactor" />

and for no reason that I can figure out, everything now works fine.  (I
swear that's all I changed, but I understand if you don't believe me.  I
wouldn't believe me either if I hadn't been fighting with this all morning.)


I had to shrug and move on... I have no idea why Tomcat won't unpack a file
with one particular name, but changing it by as little as one letter makes
it happy.

I appreciate the suggestions that were offered!

-- 
Wendy Smoak
Applications Systems Analyst, Sr.
Arizona State University PA Information Resources Management

--Boundary_(ID_qalw98rRXWYo/gglMPKG7A)--