Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 89911 invoked from network); 7 Jul 2006 10:33:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 7 Jul 2006 10:33:51 -0000 Received: (qmail 28272 invoked by uid 500); 7 Jul 2006 10:33:47 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 28099 invoked by uid 500); 7 Jul 2006 10:33:46 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: users@cocoon.apache.org List-Id: Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 28088 invoked by uid 99); 7 Jul 2006 10:33:46 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Jul 2006 03:33:46 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=NO_REAL_NAME,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of Fernando.Matomira@thomson.com designates 163.231.12.68 as permitted sender) Received: from [163.231.12.68] (HELO mailout-tlr.thomson.com) (163.231.12.68) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Jul 2006 03:33:44 -0700 Received: from mailout-tlr.thomson.com (localhost [127.0.0.1]) by mailout-tlr.thomson.com (Switch-3.2.2/Switch-3.2.0) with ESMTP id k67AXLiF022479 for ; Fri, 7 Jul 2006 10:33:21 GMT Received: from tlrusmneagfe01.ERF.THOMSON.COM (tlrusmneagfe01.erf.thomson.com [163.231.22.161]) by mailout-tlr.thomson.com (Switch-3.2.2/Switch-3.2.0) with ESMTP id k67AXL5e022476 for ; Fri, 7 Jul 2006 10:33:21 GMT Received: from tlrchbermbx01.ERF.THOMSON.COM ([10.222.232.6]) by tlrusmneagfe01.ERF.THOMSON.COM with Microsoft SMTPSVC(6.0.3790.1830); Fri, 7 Jul 2006 05:33:21 -0500 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Subject: RE: Kill the cache? Date: Fri, 7 Jul 2006 12:33:10 +0200 Message-ID: <8D8D5C193740B04894FA6AA9F767A4E501AEEAE8@tlrchbermbx01.ERF.THOMSON.COM> In-Reply-To: <44AD325D.3010709@dslextreme.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Kill the cache? Thread-Index: AcahFKKeSSSyAt/ZT7GBQ5b5WZXJVgAm7jJg From: To: X-OriginalArrivalTime: 07 Jul 2006 10:33:21.0656 (UTC) FILETIME=[C4E90780:01C6A1B0] X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Yes, it's caching the whole directories of the other contexts. I am not using hibernate or ehcache in other contexts. -----Original Message----- From: Ralph Goers [mailto:Ralph.Goers@dslextreme.com]=20 Sent: Thursday, July 06, 2006 5:55 PM To: users@cocoon.apache.org Subject: Re: Kill the cache? What do you mean it is caching other contexts? Do you mean that objects from other servlet contexts are being placed in the cache? Cocoon only caches its own content. Now I suppose it is possible that if you are using Hibernate or something else that also uses ehcache that=20 the stuff they are caching might end up in the same cache as Cocoon's,=20 but it isn't Cocoon doing this. Basically, the cache is more or less=20 just a Map. Something somewhere has to do a put to get it into the=20 cache. Nothing is just going to arbitrarily pick up random objects and store them in the cache. You can easily change Cocoon's default store=20 to use something other than ehcache. Ralph Fernando.Matomira@thomson.com wrote: >Well, I just tried with ehcache 1.2.1 and it's still caching other >contexts. > > >-----Original Message----- >From: Mato Mira, Fernando (DIA CHE)=20 >Sent: Thursday, July 06, 2006 3:12 PM >To: users@cocoon.apache.org >Subject: RE: Kill the cache? > >ehcache 1.2 uses the context classloader, not the system classloader > >Anyway, it's not that I am accessing classes across contexts, it's >that we are seeing classes being cached in other contexts. > >-----Original Message----- >From: Simone Gianni [mailto:s.gianni@thebug.it]=20 >Sent: Thursday, July 06, 2006 3:08 PM >To: users@cocoon.apache.org >Subject: Re: Kill the cache? > >In that case : >1) Check your container classloading settings, the jars of a context >should not propagate to other contextes. >2) If you don't find any suitable classloading configuration in your >container, use the paranoid cloassloader servlet instead of the default >one, that should force cocoon to use only it's own jars. > >In both cases, it's very strange (but depends on the container/JRE >configuration, so definitively possible) that a class from a context >propagates to other contextes. > >Hope this somehow helps, >Simone > >Fernando.Matomira@thomson.com wrote: > > =20 > >>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:Roland.Bair@topcall.com]=20 >>Sent: Thursday, July 06, 2006 2:47 PM >>To: users@cocoon.apache.org >>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: roland.bair@topcall.com >>----------------------------------------------------------- >> >> >> >> >> > >> a@thomson.com> >> >> >>To=20 >> 06.07.2006 14:37 >> >> >>cc=20 >> >> >> Please respond to >>Subject=20 >> users@cocoon.apac 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:flutina@gmail.com] >>Sent: Thursday, July 06, 2006 2:34 PM >>To: users@cocoon.apache.org >>Subject: Re: Kill the cache? >> >>try delete content under >>\webapps\exec\WEB-INF\work\cocoon-files\cache-dir >> >> >> >> >> >>2006/7/6,: >> >> >>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: cocoonman@gmail.com] >>Sent: Thursday, July 06, 2006 2:15 PM >>To: users@cocoon.apache.org >>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: >> >> >> >> >> >> >>Regards, >> >> >> >> >> >> >>2006/7/6, Fernando.Matomira@thomson.com >> =20 >> >: > =20 > >>This whole situation of cocoon caching other contexts is unacceptable. >> >> >> >> >> >>How do I kill the cache mechanism completely? >> >> >> >> >> >>Thanks >> >> >> >> >> >> >> >>--------------------------------------------------------------------- >>To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org >>For additional commands, e-mail: users-help@cocoon.apache.org >> >>=20 >> >> =20 >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org