Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 76899 invoked from network); 1 Jun 2000 17:24:01 -0000 Received: from balld-0.dsl.speakeasy.net (HELO localhost.localdomain) (@216.254.77.75) by locus.apache.org with SMTP; 1 Jun 2000 17:24:01 -0000 Received: from localhost (balld@localhost) by localhost.localdomain (8.9.3/8.9.3) with ESMTP id MAA16209 for ; Thu, 1 Jun 2000 12:14:40 -0400 X-Authentication-Warning: localhost.localdomain: balld owned process doing -bs Date: Thu, 1 Jun 2000 12:14:39 -0400 (EDT) From: Donald Ball X-Sender: balld@localhost.localdomain To: Cocoon Dev Subject: Re: Cache problems with 1.7.4 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On Thu, 1 Jun 2000, Jeremy Quinn wrote: > Dear All, > > I thought all cache issues in 1.7.4 were fixed, but they appear not to be. > > I have been building a project that has 3 XSLs, one that chooses and two > that output different data types. > > (I find it is not possible to have one XSL choose dynamically which > cocoon-process type to use.) > > I found (to my dismay :) that the second set of XSLs in the chain are never > reloaded if they are modified, even if I "touch" the first ... only a > server restart reloads the modified XSL if it is >= second in the chain. I have similar problems with a reactor pipeline consisting of one xslt, one xsp, and another xslt. Sometimes changes to either of the xslt's don't take effect. I was never able to reduce it to a simple reproducible example, though. Here's hoping you can. :) - donald