I am using caching no problem (though I am not on the very latest HEAD
branch, but a few months old).  Given that you are upgrading from an older
cocoon version, have you checked out the documentation to ensure that you
have caching configured correctly?  If you have the samples running
http://{yourintallation}/cocoon/status should give you a clue if anything is
being cached at all.

Geoff Howard

> -----Original Message-----
> From: Albertsen, Juergen [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 28, 2002 4:53 AM
> To: [EMAIL PROTECTED]
> Subject: Cache broken in Cocoon 2.1-dev?
> 
> 
> Hi,
> 
> since switching to Cocoon 2.1-dev I noticed a considerable loss in
> performance. My website (http://www.juergenalbertsen.com) 
> currently consits
> mainly of static XML files piped through a number of XSL 
> files. There's only
> one XSP generated section, the rest is merely static. 
> 
> I looked into the cache directories that were filled with 
> pre-generaed HTML
> files when using Cocoon 2.0.2. Now they are empty. I searched 
> the mailing
> lists - both dev and user - but could not find any hint that 
> people are
> working on the cache system. Additionally, when trying the "plain"
> cocoon.war I cannot find any genared HTML files neither (so 
> doesn't seem to
> be misconfiguration). 
> 
> All this applies to a number of platforms (Windows, Linux, 
> FreeBSD) and
> Servlet containers (Resin, Tomcat). 
> 
> Thanks in adavance for your help.
> 
> Regards,
> 
> Jürgen
> 
> ---------------------------------------------------------------------
> Please check that your question  has not already been answered in the
> FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>
> 
> To unsubscribe, e-mail:     <[EMAIL PROTECTED]>
> For additional commands, e-mail:   <[EMAIL PROTECTED]>
> 

---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Reply via email to