Return-Path: 
 <tomcat-dev-return-47057-apmail-jakarta-tomcat-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-dev-archive@www.apache.org
Received: (qmail 6803 invoked from network); 14 Jul 2004 19:32:14 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 14 Jul 2004 19:32:14 -0000
Received: (qmail 36348 invoked by uid 500); 14 Jul 2004 19:32:05 -0000
Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org
Received: (qmail 36292 invoked by uid 500); 14 Jul 2004 19:32:05 -0000
Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:tomcat-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:tomcat-dev-help@jakarta.apache.org>
List-Post: <mailto:tomcat-dev@jakarta.apache.org>
List-Id: "Tomcat Developers List" <tomcat-dev.jakarta.apache.org>
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Delivered-To: mailing list tomcat-dev@jakarta.apache.org
Received: (qmail 36266 invoked by uid 99); 14 Jul 2004 19:32:05 -0000
X-ASF-Spam-Status: No, hits=0.1 required=10.0
	tests=DNS_FROM_RFC_ABUSE
X-Spam-Check-By: apache.org
Received: from [12.11.148.30] (HELO mxrelay.ptc.com) (12.11.148.30)
  by apache.org (qpsmtpd/0.27.1) with ESMTP; Wed, 14 Jul 2004 12:32:01 -0700
Received: from HQ-EXFE2.ptcnet.ptc.com (hq-exfe2.ptcnet.ptc.com
 [132.253.201.63])
	by mxrelay.ptc.com (8.12.10/8.12.10) with ESMTP id i6EJVx0j012377
	for <tomcat-dev@jakarta.apache.org>; Wed, 14 Jul 2004 15:31:59 -0400 (EDT)
Received: from [132.253.9.102] ([132.253.9.102]) by HQ-EXFE2.ptcnet.ptc.com
 with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 14 Jul 2004 15:31:59 -0400
Message-ID: <40F58A2E.1030405@ptc.com>
Date: Wed, 14 Jul 2004 14:31:58 -0500
From: Jess Holle <jessh@ptc.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.7) Gecko/20040616
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tomcat Developers List <tomcat-dev@jakarta.apache.org>
Subject: Re: Some JK2 ideas
References: <200407141845.i6EIjchb024567@pop.xnet.hr>
In-Reply-To: <200407141845.i6EIjchb024567@pop.xnet.hr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 14 Jul 2004 19:31:59.0376 (UTC)
 FILETIME=[3B1C8100:01C469D9]
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Mladen Turk wrote:

>>-----Original Message-----
>>From: Bill Barker
>>
>>Having the option to do per-host and even per-context configs 
>>makes life much easier for admins of servers that support it. 
>> Otherwise, you end up with a file that looks like:
>>   <jk-config>
>>     &host1;
>>     &host2;
>>     &host3;
>>  </jk-config>
>>which is fine for xml-hackers, but not very helpful for server-admins.
>>    
>>
>Yes, that's true, but that same layz admin still has to make the Tomcat
>running, or not?
>It still has to learn that server.xml stuff, and even make it working :)
>
>Who ever asked the poor apache admin  about the TC's config ater all?
>  
>
It really does not matter who the admin is.  Even a sophisticated admin 
is going to want to have file modification dates they can trust on 
various aspects of the configuration so they can answer "did I change 
this part?" questions.

Using a modular multi-XML-file approach does not pollute the result with 
any additional server-specific or Tomcat-specific baggage.  It just 
makes management and automated configuration/installation much more 
workable.

--
Jess Holle


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