Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <1360072865.5363.1.camel@mail.remm.hd.free.fr>
Subject: Re: [Proposal] Resurrecting storeconfig
From: Remy Maucherat <remm@apache.org>
To: dev@tomcat.apache.org
Date: Tue, 05 Feb 2013 15:01:05 +0100
In-Reply-To: 
 <CAHHaTeGLag9Fr0Y01QbuHMrb6v7Z4GAYM1JDPhnv49sTuqKGOw@mail.gmail.com>
References: <1355492176.3412.10.camel@mail.remm.hd.free.fr>
	 <50CB615E.7000700@apache.org>
	 <1359751634.12053.1.camel@mail.remm.hd.free.fr>
	 <510F9121.4070901@gmail.com>
	 <CAHHaTeGLag9Fr0Y01QbuHMrb6v7Z4GAYM1JDPhnv49sTuqKGOw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit

On Tue, 2013-02-05 at 19:27 +0900, Keiichi Fujino wrote:
> Hi.
> 
> I do not understand about StoreConfig well, but I have a question.
> 
> As long as I read the code (r1442161), I think that storeconfig() seem
> to trigger a redeployment of Web applications.
> For example, new context.xml will be created when
> testApp/META-INF/context.xml is stored.
> And redeployment of this new context.xml will be done by HostConfig.
> Is this a design ?
> I think better that storeconfig () does not trigger a redeployment of
> the Web application.

Yes, storeconfig will saved these (settings could have been changed).
Then the deployer sees the updated descriptor, and it redeploys the
webapp.

Rémy


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