Return-Path: 
 <users-return-198502-apmail-tomcat-users-archive=tomcat.apache.org@tomcat.apache.org>
Delivered-To: apmail-tomcat-users-archive@www.apache.org
Received: (qmail 17567 invoked from network); 24 Jun 2009 23:11:22 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 24 Jun 2009 23:11:22 -0000
Received: (qmail 90105 invoked by uid 500); 24 Jun 2009 23:11:29 -0000
Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org
Received: (qmail 90040 invoked by uid 500); 24 Jun 2009 23:11:29 -0000
Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@tomcat.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@tomcat.apache.org>
List-Post: <mailto:users@tomcat.apache.org>
List-Id: <users.tomcat.apache.org>
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Delivered-To: mailing list users@tomcat.apache.org
Received: (qmail 90029 invoked by uid 99); 24 Jun 2009 23:11:29 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jun 2009 23:11:29 +0000
X-ASF-Spam-Status: No, hits=-4.0 required=10.0
	tests=RCVD_IN_DNSWL_MED,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: local policy)
Received: from [192.61.61.104] (HELO usea-naimss2.unisys.com) (192.61.61.104)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jun 2009 23:11:18 +0000
Received: from usea-nagw2.na.uis.unisys.com ([129.224.72.18]) by usea-naimss2
 with InterScan Message Security Suite; Wed, 24 Jun 2009 18:10:55 -0500
Received: from usea-nagw2.na.uis.unisys.com ([129.224.72.53]) by
 usea-nagw2.na.uis.unisys.com with Microsoft SMTPSVC(6.0.3790.3959);
	 Wed, 24 Jun 2009 18:10:56 -0500
Received: from usea-nahubcas1.na.uis.unisys.com ([129.224.76.114]) by
 usea-nagw2.na.uis.unisys.com with Microsoft SMTPSVC(6.0.3790.3959);
	 Wed, 24 Jun 2009 18:10:56 -0500
Received: from USEA-EXCH7.na.uis.unisys.com ([129.224.76.38]) by
 usea-nahubcas1.na.uis.unisys.com ([129.224.76.114]) with mapi; Wed, 24 Jun
 2009 18:10:56 -0500
From: "Caldarale, Charles R" <Chuck.Caldarale@unisys.com>
To: Tomcat Users List <users@tomcat.apache.org>
Date: Wed, 24 Jun 2009 18:10:51 -0500
Subject: RE: The best place for implementing context specific behavior?
Thread-Topic: The best place for implementing context specific behavior?
Thread-Index: Acn1GsvHf32khzVhTVysTGcfJvnAqwABSXIw
Message-ID: 
 <0AAE5AB84B013E45A7B61CB66943C1722947D7C626@USEA-EXCH7.na.uis.unisys.com>
References: <f5af14000906241108w7e2d7f94r9ea4eea359ce7b3c@mail.gmail.com>
	 	<4A42943A.1080307@ice-sa.com>
 	<f5af14000906241413ne24e9cbg21c559905bfbbef0@mail.gmail.com>
 <4A42A77E.8040706@ice-sa.com>
In-Reply-To: <4A42A77E.8040706@ice-sa.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-cr-hashedpuzzle: jlw= ASEC ArSL A5m1 BGP6 Bj2p B+nW C305 C4pX DdIS DewI
 GlOx IQzD I3GS JcE4
 JgJl;1;dQBzAGUAcgBzAEAAdABvAG0AYwBhAHQALgBhAHAAYQBjAGgAZQAuAG8AcgBnAA==;Sosha1_v1;7;{99C89707-9EB4-457F-B844-A170E5BBD7D5};YwBoAHUAYwBrAC4AYwBhAGwAZABhAHIAYQBsAGUAQAB1AG4AaQBzAHkAcwAuAGMAbwBtAA==;Wed,
 24 Jun 2009 23:10:51
 GMT;UgBFADoAIABUAGgAZQAgAGIAZQBzAHQAIABwAGwAYQBjAGUAIABmAG8AcgAgAGkAbQBwAGwAZQBtAGUAbgB0AGkAbgBnACAAYwBvAG4AdABlAHgAdAAgAHMAcABlAGMAaQBmAGkAYwAgAGIAZQBoAGEAdgBpAG8AcgA/AA==
x-cr-puzzleid: {99C89707-9EB4-457F-B844-A170E5BBD7D5}
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 24 Jun 2009 23:10:56.0317 (UTC)
 FILETIME=[075F1ED0:01C9F521]
X-Virus-Checked: Checked by ClamAV on apache.org

> From: Andr=E9 Warnier [mailto:aw@ice-sa.com]
> Subject: Re: The best place for implementing context specific behavior?
>=20
> I believe (but we need a real expert here) that having multiple <Host>
> entries sharing the same appBase is a receipe for problems.

It seems to work for most usages.  As Mark pointed out, each <Host> or <Con=
text> should have separate work directories to avoid conflicts with temp fi=
les, JSPs, etc.

> If it is really just to have a single copy of the code on disk however,
> you may be able to get away with having multiple (differently named)
> appBase attributes, but all symlinked to the same physical location

That will make no difference, since the underlying location is the same for=
 all.

> I must say that I don't really understand the requirement, unless your
> "fruit" webapp is really big (in disk size), or you have many different
> "fruit" hosts.

It's not clear to me that the OP wants separate instances of one webapp (on=
e per host), or if he wants one instance of one webapp that services all ho=
sts.  We really need that clarified before any further suggestions can be m=
ade.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MA=
TERIAL and is thus for use only by the intended recipient. If you received =
this in error, please contact the sender and delete the e-mail and its atta=
chments from all computers.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org