I think the problem might be that Cocoon is shipping with ehcache 1.1,
which seems to exhibit "singleton behavior".

-----Original Message-----
From: Roland Bair [mailto:[EMAIL PROTECTED] 
Sent: Thursday, July 06, 2006 2:47 PM
To: [email protected]
Subject: RE: Kill the cache?


maybe u should specify which other context cocoon might cache?

only request on your sitemap are processed by cocoon, aren't they?


reg.

Roland Bair
Research & Development
Topcall International AG
A-1230 Wien, Talpagasse 1

Mail: [EMAIL PROTECTED]
-----------------------------------------------------------


 

             <Fernando.Matomir

             [EMAIL PROTECTED]>

 
To 
             06.07.2006 14:37          <[email protected]>

 
cc 
 

             Please respond to
Subject 
             [EMAIL PROTECTED]         RE: Kill the cache?

                  he.org

 

 

 

 

 





I don't want to remove what has been cached, I want cocoon to stop
caching
my other contexts.



From: Zhu Di [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 06, 2006 2:34 PM
To: [email protected]
Subject: Re: Kill the cache?

try delete content under
\webapps\exec\WEB-INF\work\cocoon-files\cache-dir





2006/7/6,<[EMAIL PROTECTED]>:


I don't want to disable it in the pipeline. I want to remove the cache
mechanism completely


because it's caching other contexts, and nobody put that in any
pipeline.





Thanks






From: Cocoon Man [mailto: [EMAIL PROTECTED]
Sent: Thursday, July 06, 2006 2:15 PM
To: [email protected]
Subject: Re: Kill the cache?





Hello Fernando,





To disable default Cocoon cache mechanism, just indicate that you want
to
use a "noncaching" pipeline in your sitemap.xmap file:


<map:pipeline type="noncaching">



Regards,






2006/7/6, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:


This whole situation of cocoon caching other contexts is unacceptable.





How do I kill the cache mechanism completely?





Thanks







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

Reply via email to