Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 88631 invoked by uid 500); 2 Apr 2001 11:30:37 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 88610 invoked from network); 2 Apr 2001 11:30:34 -0000 To: cocoon-dev@xml.apache.org Subject: Re: [C2]: Sitemap reloading Message-ID: <986211031.3ac862d7dd4c3@mail.otego.com> Date: Mon, 02 Apr 2001 13:30:31 +0200 (CEST) From: Giacomo Pati References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.4 X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Quoting Carsten Ziegeler : > Hi, > > sorry I am now a little bit confused about all this sitemap reloading > stuff.... > Perhaps someone can help me out of this, please. > > This is the story I though it was true until today: > > 1. If the sitemap is modified, it is recompiled. > 2. The recompilation is in the background. > 3. Until the recompilation is not finished the old sitemap is used. > 4. using the cocoon-reload parameter, a recompilation is forced if the > sitemap has been modified, the sitemap is compiled and the request is > served with the new sitemap. > > This is exactly the way, C2 works with Tomcat 3.2.1. But looking into > the code for this (CocoonServlet mainly) I didn't recognize parts 2-4. > The ongoing discussion from today about the cocoon-reload parameter > showed that maybe my understanding is wrong: > > The getCocoon() method gets a new Cocoon instance, if > 1. The sitemap has been modified > 2. The cocoon-reload parameter is specified and the request.pathInfo is > null > 3. If no Cocoon instance is available, the cocoon-reload parameter > specified and the request.pathInfo is null. > > But where is the compilation in the background specified? I must be > blind - I don't see it. Oh, it's in the sitemap package itself. The .sitemap.Handler is responsible for the compilation of the sitemap and the .sitemap.Manager triggers recompilation based on the modify date. The CocoonServlet is only able to say "reload the sitemap" but has no change to say "do a recompilation". Giacomo --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org