Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 49297 invoked from network); 14 Feb 2003 16:14:54 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 14 Feb 2003 16:14:54 -0000 Received: (qmail 28512 invoked by uid 97); 14 Feb 2003 16:16:26 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@nagoya.betaversion.org Received: (qmail 28505 invoked from network); 14 Feb 2003 16:16:25 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 14 Feb 2003 16:16:25 -0000 Received: (qmail 47741 invoked by uid 500); 14 Feb 2003 16:14:36 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 47720 invoked from network); 14 Feb 2003 16:14:36 -0000 Received: from mailgate5.thehartford.com (199.222.4.86) by daedalus.apache.org with SMTP; 14 Feb 2003 16:14:36 -0000 Received: from ct00ntsms02.thehartford.com (ct00ntsms02.thehartford.com [157.209.173.232]) by mailgate5.thehartford.com (Switch-2.2.4/Switch-2.2.4) with ESMTP id h1EGEYP03325 for ; Fri, 14 Feb 2003 11:14:34 -0500 (EST) Received: from ct00excim02.thehartford.com (unverified) by ct00ntsms02.thehartford.com (Content Technologies SMTPRS 4.2.10) with ESMTP id for ; Fri, 14 Feb 2003 11:14:32 -0500 Received: by ct00excim02.thehartford.com with Internet Mail Service (5.5.2653.19) id <1T1K5J4P>; Fri, 14 Feb 2003 11:14:32 -0500 Message-ID: <39B759FF5B2BD411A2C900508B6CDC061063F79E@ct01excmb05.thehartford.com> From: "White, Joshua A (CASD, IT)" To: "'tomcat-user@jakarta.apache.org'" Subject: Web app configuration problems Date: Fri, 14 Feb 2003 11:14:26 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I am hoping someone could explain how Tomcat uses context paths. In my server.xml file, I have declared a seperate context and some JNDI resources for /myapp-web. The way I deploy my web application determines if these resources will be available or not. If I drop my web applications war file (myapp-web.war) into %CATALINA_HOME%/webapps, I am golden (The war does not even unpack). However, if I use the manager utility from ant, the resources are not available. I have checked to make sure that ant installs the application correctly. I receive the following message from ant: [echo] OK - Installed application at context path /myapp-web This utility seems to place an unpacked version of the war file into the %CATALINA_HOME%\work\Standalone\localhost directory. This does not seem to be enough. If I manually drop the war into the webapps directory, everything works again. If I deploy using only the manager utility, how should I configure its JNDI resources so they work? -Joshua This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-user-help@jakarta.apache.org