Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 36445 invoked by uid 500); 24 Sep 2001 22:17:25 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: tomcat-dev@jakarta.apache.org Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 36436 invoked from network); 24 Sep 2001 22:17:25 -0000 Date: Mon, 24 Sep 2001 15:22:40 -0700 (PDT) From: X-X-Sender: To: Subject: Re: [PATCH]: TC 3.3 ReloadInterceptor: Local Interceptors -> Feedbackwanted In-Reply-To: <3BAFAFB9.A134DFB1@binarix.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: localhost.apache.org 1.6.2 0/1000/N On Tue, 25 Sep 2001, Bojan Smojver wrote: > cmanolache@yahoo.com wrote: > > > > Hi Bojan, > > > > +1 - looks very good, it'll be a great 'first commit'. > > > > ( 'normal' case with only global modules is not affected in any way, and > > for local modules it'll do the right thing, and update the context ). > > Thanks. Wouldn't be able to do any of it without your guidance. Well, you were right in the first place - we need a mechanism to detect changes in the config and reconfigure, taking into account the new app-foo.xml file. And your initial solutions is probably better - and could solve part of the 'reconfigure' issue. Maybe later ( after 3.3 ) we could revisit this issue and improve a bit ContextXmlReader. Costin