Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 391 invoked by uid 500); 13 May 2003 18:04:20 -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 356 invoked from network); 13 May 2003 18:04:20 -0000 Received: from anchor-post-30.mail.demon.net (194.217.242.88) by daedalus.apache.org with SMTP; 13 May 2003 18:04:20 -0000 Received: from media.demon.co.uk ([80.177.14.141]) by anchor-post-30.mail.demon.net with esmtp (Exim 3.35 #1) id 19Fe8V-000AUy-0U for cocoon-dev@xml.apache.org; Tue, 13 May 2003 19:04:23 +0100 Date: Tue, 13 May 2003 19:04:21 +0100 Mime-Version: 1.0 (Apple Message framework v552) Content-Type: text/plain; delsp=yes; charset=US-ASCII; format=flowed Subject: invalid caching problem From: Jeremy Quinn To: cocoon-dev@xml.apache.org Content-Transfer-Encoding: 7bit Message-Id: <52788C4E-856D-11D7-9F6D-0003935AD2EE@media.demon.co.uk> X-Mailer: Apple Mail (2.552) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi All I mentioned this problem a while ago but got no feedback, so I am trying again .... On a site I am working on, when I edit an XML file, accessed by the file generator, I do not see the changes in the output when reloaded. This started happening several months ago. The only way I have found of seeing the changes is to force cocoon to trash it's cache, it's a PIA ;) What is weird is that simple samples distributed with Cocoon work fine! Below are the relevant snippets from my sitemap, it is mounted by the main dist sitemap. 1024 -//W3C//DTD HTML 4.01 Transitional//EN http://www.w3.org/TR/1999/REC-html401-19991224/ loose.dtd UTF-8 yes I have tried the desperate approach of cutting out, bit by bit everything extraneous to see if the problem ever goes away, with no luck so far. Changing XSLT works as expected. Changing one of the 'components' that gets CIncluded works as expected. It is only the file that starts the pipeline that fails to invalidate the cache when edited. Am I doing something incorrectly in the Sitemap, or is there some bug that arises out of my particular usage? Any help with this, or guidance on finding (from debug logs) which component is acting incorrectly, would be gratefully received. regards Jeremy