Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: pass (asf.osuosl.org: domain of Fernando.Matomira@thomson.com
 designates 163.231.12.68 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Kill the cache?
Date: Thu, 6 Jul 2006 15:42:41 +0200
Message-ID: 
 <8D8D5C193740B04894FA6AA9F767A4E501AEEA23@tlrchbermbx01.ERF.THOMSON.COM>
In-Reply-To: 
 <8D8D5C193740B04894FA6AA9F767A4E501AEEA11@tlrchbermbx01.ERF.THOMSON.COM>
Thread-Topic: Kill the cache?
Thread-Index: Acag/VH8ZYqK871eSaSOeLeb6AhwrQAACSoAAAEZ77A=
From: <Fernando.Matomira@thomson.com>
To: <users@cocoon.apache.org>

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:

>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
>-----------------------------------------------------------
>
>
>=20
>
>             <Fernando.Matomir
>
>             a@thomson.com>
>
>=20
>To=20
>             06.07.2006 14:37          <users@cocoon.apache.org>
>
>=20
>cc=20
>=20
>
>             Please respond to
>Subject=20
>             users@cocoon.apac         RE: Kill the cache?
>
>                  he.org
>
>=20
>
>=20
>
>=20
>
>=20
>
>=20
>
>
>
>
>
>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,<Fernando.Matomira@thomson.com>:
>
>
>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:
>
>
><map:pipeline type=3D"noncaching">
>
>
>
>Regards,
>
>
>
>
>
>
>2006/7/6, Fernando.Matomira@thomson.com
<Fernando.Matomira@thomson.com>:
>
>
>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
Simone Gianni

---------------------------------------------------------------------
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


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org