You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Fe...@thomson.com on 2006/07/06 14:04:16 UTC
Kill the cache?
This whole situation of cocoon caching other contexts is unacceptable.
How do I kill the cache mechanism completely?
Thanks
Re: Kill the cache?
Posted by Scott Warren <ap...@gmail.com>.
Check your sent mail. It's a GMail thing.
regards
Scott Warren
On 7/6/06, Zhu Di <fl...@gmail.com> wrote:
>
> I am really sorry to asking this question here, but seems this mail is the
> > only one I can receive from this mail-list...
>
>
> how can I get all mails from this mailling-list? and when I try to
> initiate a new topic, should I send mail to users@apache.org, right?
>
> but why I can't receive anything, including the mail I sent to the above
> address?
>
> please, help me
>
> flutina
>
>
>
>
Re: Kill the cache?
Posted by Zhu Di <fl...@gmail.com>.
>
> I am really sorry to asking this question here, but seems this mail is the
> only one I can receive from this mail-list...
how can I get all mails from this mailling-list? and when I try to initiate
a new topic, should I send mail to users@apache.org, right?
but why I can't receive anything, including the mail I sent to the above
address?
please, help me
flutina
RE: Kill the cache?
Posted by Fe...@thomson.com.
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]
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
the stuff they are caching might end up in the same cache as Cocoon's,
but it isn't Cocoon doing this. Basically, the cache is more or less
just a Map. Something somewhere has to do a put to get it into the
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
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)
>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]
>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]
>>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
>>-----------------------------------------------------------
>>
>>
>>
>>
>> <Fernando.Matomir
>>
>> a@thomson.com>
>>
>>
>>To
>> 06.07.2006 14:37 <us...@cocoon.apache.org>
>>
>>
>>cc
>>
>>
>> Please respond to
>>Subject
>> 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,<Fe...@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="noncaching">
>>
>>
>>
>>Regards,
>>
>>
>>
>>
>>
>>
>>2006/7/6, Fernando.Matomira@thomson.com
>>
>>
><Fe...@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
>>
>>
>>
>>
>>
---------------------------------------------------------------------
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
Re: Kill the cache?
Posted by Ralph Goers <Ra...@dslextreme.com>.
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
the stuff they are caching might end up in the same cache as Cocoon's,
but it isn't Cocoon doing this. Basically, the cache is more or less
just a Map. Something somewhere has to do a put to get it into the
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
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)
>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]
>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]
>>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
>>-----------------------------------------------------------
>>
>>
>>
>>
>> <Fernando.Matomir
>>
>> a@thomson.com>
>>
>>
>>To
>> 06.07.2006 14:37 <us...@cocoon.apache.org>
>>
>>
>>cc
>>
>>
>> Please respond to
>>Subject
>> 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,<Fe...@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="noncaching">
>>
>>
>>
>>Regards,
>>
>>
>>
>>
>>
>>
>>2006/7/6, Fernando.Matomira@thomson.com
>>
>>
><Fe...@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
>>
>>
>>
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
RE: Kill the cache?
Posted by Fe...@thomson.com.
Well, I just tried with ehcache 1.2.1 and it's still caching other
contexts.
-----Original Message-----
From: Mato Mira, Fernando (DIA CHE)
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]
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]
>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
>-----------------------------------------------------------
>
>
>
>
> <Fernando.Matomir
>
> a@thomson.com>
>
>
>To
> 06.07.2006 14:37 <us...@cocoon.apache.org>
>
>
>cc
>
>
> Please respond to
>Subject
> 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,<Fe...@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="noncaching">
>
>
>
>Regards,
>
>
>
>
>
>
>2006/7/6, Fernando.Matomira@thomson.com
<Fe...@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
>
>
>
--
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
RE: Kill the cache?
Posted by Fe...@thomson.com.
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]
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]
>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
>-----------------------------------------------------------
>
>
>
>
> <Fernando.Matomir
>
> a@thomson.com>
>
>
>To
> 06.07.2006 14:37 <us...@cocoon.apache.org>
>
>
>cc
>
>
> Please respond to
>Subject
> 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,<Fe...@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="noncaching">
>
>
>
>Regards,
>
>
>
>
>
>
>2006/7/6, Fernando.Matomira@thomson.com
<Fe...@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
>
>
>
--
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
Re: Kill the cache?
Posted by Simone Gianni <s....@thebug.it>.
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]
>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
>-----------------------------------------------------------
>
>
>
>
> <Fernando.Matomir
>
> a@thomson.com>
>
>
>To
> 06.07.2006 14:37 <us...@cocoon.apache.org>
>
>
>cc
>
>
> Please respond to
>Subject
> 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,<Fe...@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="noncaching">
>
>
>
>Regards,
>
>
>
>
>
>
>2006/7/6, Fernando.Matomira@thomson.com <Fe...@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
>
>
>
--
Simone Gianni
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
RE: Kill the cache?
Posted by Fe...@thomson.com.
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]
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
-----------------------------------------------------------
<Fernando.Matomir
a@thomson.com>
To
06.07.2006 14:37 <us...@cocoon.apache.org>
cc
Please respond to
Subject
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,<Fe...@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="noncaching">
Regards,
2006/7/6, Fernando.Matomira@thomson.com <Fe...@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
RE: Kill the cache?
Posted by Roland Bair <Ro...@topcall.com>.
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
-----------------------------------------------------------
<Fernando.Matomir
a@thomson.com>
To
06.07.2006 14:37 <us...@cocoon.apache.org>
cc
Please respond to Subject
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,<Fe...@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="noncaching">
Regards,
2006/7/6, Fernando.Matomira@thomson.com <Fe...@thomson.com>:
This whole situation of cocoon caching other contexts is unacceptable.
How do I kill the cache mechanism completely?
Thanks
RE: Kill the cache?
Posted by Fe...@thomson.com.
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,<Fe...@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="noncaching">
Regards,
2006/7/6, Fernando.Matomira@thomson.com <Fe...@thomson.com>:
This whole situation of cocoon caching other contexts is unacceptable.
How do I kill the cache mechanism completely?
Thanks
Re: Kill the cache?
Posted by Zhu Di <fl...@gmail.com>.
try delete content under \webapps\exec\WEB-INF\work\cocoon-files\cache-dir
2006/7/6, Fernando.Matomira@thomson.com <Fe...@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="noncaching">
>
>
> Regards,
>
>
>
>
> 2006/7/6, Fernando.Matomira@thomson.com <Fe...@thomson.com>:
>
> This whole situation of cocoon caching other contexts is unacceptable.
>
>
>
> How do I kill the cache mechanism completely?
>
>
>
> Thanks
>
>
>
>
>
RE: Kill the cache?
Posted by Fe...@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="noncaching">
Regards,
2006/7/6, Fernando.Matomira@thomson.com <Fe...@thomson.com>:
This whole situation of cocoon caching other contexts is unacceptable.
How do I kill the cache mechanism completely?
Thanks
Re: Kill the cache?
Posted by Cocoon Man <co...@gmail.com>.
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, Fernando.Matomira@thomson.com <Fe...@thomson.com>:
>
> This whole situation of cocoon caching other contexts is unacceptable.
>
>
>
> How do I kill the cache mechanism completely?
>
>
>
> Thanks
>
>
>
Re: Kill the cache?
Posted by Thomas Markus <t....@proventis.net>.
may be you make your caching pipeline processor a non caching
<map:pipes default="noncaching">
<map:pipe name="caching"
src="org.apache.cocoon.components.pipeline.impl.NonCachingProcessingPipeline"/>
<map:pipe name="noncaching"
src="org.apache.cocoon.components.pipeline.impl.NonCachingProcessingPipeline"/>
</map:pipes>
or you remove the caching type und you got failures if somewhere a
caching pipeline is defined
Thomas
Fernando.Matomira@thomson.com schrieb:
>
> This whole situation of cocoon caching other contexts is unacceptable.
>
>
>
> How do I kill the cache mechanism completely?
>
>
>
> Thanks
>
>
>
--
Thomas Markus
Tel: +49 30 29 36 399 - 22
Fax: +49 30 29 36 399 - 50
Mail: t.markus@proventis.net
Web: www.proventis.net
Web: www.blue-ant.de
proventis GmbH
Zimmerstraße 79-80
10117 Berlin
"proventis: Wir bewegen Organisationen."