cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeremy Quinn <jer...@media.demon.co.uk>
Subject invalid caching problem
Date Tue, 13 May 2003 18:04:21 GMT
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.

<map:components>
   <map:generators default="file"/>
   <map:transformers default="xalan">
   <map:transformer logger="sitemap.transformer.cinclude" name="include"
     pool-grow="2" pool-max="16" pool-min="2"
     src="org.apache.cocoon.transformation.CIncludeTransformer"/>
   </map:transformers>
   <map:readers default="resource"/>
   <map:matchers default="wildcard"/>
   <map:selectors default="browser"/>
   <map:serializers default="html">
     <map:serializer logger="sitemap.serializer.html"  
mime-type="text/html"
         name="html-4.0" pool-grow="4" pool-max="32" pool-min="4"
         src="org.apache.cocoon.serialization.HTMLSerializer">
       <buffer-size>1024</buffer-size>
       <doctype-public>-//W3C//DTD HTML 4.01  
Transitional//EN</doctype-public>
        
<doctype-system>http://www.w3.org/TR/1999/REC-html401-19991224/ 
loose.dtd</doctype-system>
       <encoding>UTF-8</encoding>
       <omit-xml-declaration>yes</omit-xml-declaration>
     </map:serializer>
   </map:serializers>
</map:components>

<map:resources>
   <map:resource name="file">
     <map:transform src="{client:xslt}/prepare-include.xsl">
       <map:parameter name="components" value="{client:component}"/>
     </map:transform>
     <map:transform type="include"/>
     <map:call resource="html"/>
   </map:resource>

   <!-- snip - more resources -->

   <map:resource name="html">
     <map:transform src="{client:xslt}/process-components.xsl"  
label="search">
       <map:parameter name="res" value="{../res}"/>
     </map:transform>
     <map:transform src="{client:xslt}/make-chapter-links.xsl"/>
     <map:transform src="{client:xslt}/doc2html.xsl">
       <map:parameter name="asset" value="{client:asset}"/>
       <map:parameter name="res" value="{../res}"/>
       <map:parameter name="prefix" value="{../prefix}"/>
       <map:parameter name="_display" value="{../display}"/>
     </map:transform>
     <map:serialize type="html-4.0"/>
   </map:resource>
</map:resources>

<!-- snip - other pipelines -->

<map:pipeline>
   <map:parameter name="expires" value="access plus 120 minutes"/>

   <!-- home page -->
   <map:match pattern="^(easy/)?index$" type="regexp">
     <map:generate src="{client:content}/index.xml"/>
     <map:call resource="file">
       <map:parameter name="res" value="index"/>
       <map:parameter name="display" value="{1}"/>
     </map:call>
   </map:match>

   <!-- snip other matchers -->

</map:pipeline>


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


Mime
View raw message