Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 44574 invoked from network); 16 Jun 2003 22:11:28 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 16 Jun 2003 22:11:28 -0000 Received: (qmail 21435 invoked by uid 97); 16 Jun 2003 22:13:53 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@nagoya.betaversion.org Received: (qmail 21428 invoked from network); 16 Jun 2003 22:13:52 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 16 Jun 2003 22:13:52 -0000 Received: (qmail 43748 invoked by uid 500); 16 Jun 2003 22:11:21 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 43733 invoked from network); 16 Jun 2003 22:11:21 -0000 Received: from prv-mail20.provo.novell.com (137.65.81.122) by daedalus.apache.org with SMTP; 16 Jun 2003 22:11:21 -0000 Received: from INET-PRV-MTA by prv-mail20.provo.novell.com with Novell_GroupWise; Mon, 16 Jun 2003 16:11:27 -0600 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.5.1 Date: Mon, 16 Jun 2003 16:11:15 -0600 From: "Jeff Tulley" To: Subject: Renaming /admin and /manager contexts (from user list) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N This is a conversation we are having on the users list. I propose that the contexts, "/admin", and "/manager" be renamed to something else, (I suggest "/tomcat/admin", and "/tomcat/manager" respectively). Doing so avoids Tomcat being yet another app, which wants to own http://(url)/admin This is very easily modifiable in Tomcat (one string in admin.xml and manager.xml), and I think it should be done. Original posts: (my email) Tomcat ought to do the same, IMO. You never know who else wants to own "http://url/admin", and you do not always have the luxury of renaming it. /tomcat/admin and /tomcat/manager are more specific, and can easily be changed on Tomcat's side. Maybe something to bring up on the developer list. Jeff Tulley (jtulley@novell.com) (801)861-5322 Novell, Inc., The Leading Provider of Net Business Solutions http://www.novell.com >>> dom@rucus.ru.ac.za 6/16/03 1:29:52 PM >>> That's a good point. There I go again. Always thinking of the Quick fix! ----- Original Message ----- From: Phillip Qin To: 'Tomcat Users List' Sent: Monday, June 16, 2003 9:26 PM Subject: RE: Can't get to /admin dir of our webapp I strongly disagree with all of you. Suppose you are upgrading from 4.1.18 to 4.1.24. The unpacked tar will override all of the contents re admin and install its admin app. Why don't you guys think of renaming your own admin app to something like myappadmin? -----Original Message----- From: Jeff Tulley [mailto:JTULLEY@novell.com] Sent: June 16, 2003 3:20 PM To: tomcat-user@jakarta.apache.org Subject: RE: Can't get to /admin dir of our webapp I've moved ours to be /tomcat/admin, so the we still have the admin functionality, but in a less generic name. It is just a simple change in webapps/admin.xml Jeff Tulley (jtulley@novell.com) (801)861-5322 Novell, Inc., The Leading Provider of Net Business Solutions http://www.novell.com --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org