Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Message-ID: <3F9009FD.7060507@apache.org>
Date: Fri, 17 Oct 2003 17:25:49 +0200
From: Remy Maucherat <remm@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.5) Gecko/20031007
MIME-Version: 1.0
To: Tomcat Developers List <tomcat-dev@jakarta.apache.org>
Subject: Re: [5.0] Property replacement
References: <20031017141533.24643.qmail@nagoya.betaversion.org>
 <3F900538.7030108@apache.org> <3F90070A.2020501@apache.org>
In-Reply-To: <3F90070A.2020501@apache.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Henri Gomez wrote:
> +1
> 
> The save could be implemented by saving all the discovered properties
> to an another xml file which will be load at next start time ?

That won't work: the save-to-XML blindly introspects the objects and 
saves the results.

Actually, I think we have found a neat feature addition for Tomcat.next: 
abstract the configuration storage and make it R/W. JNDI DirContext 
could be the API, but it's not a perfect fit (we'd need a naming scheme).

Remy


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