cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Donald Ball <>
Subject Re: AW: [c2] still having caching problems
Date Wed, 09 May 2001 06:29:52 GMT
On Wed, 9 May 2001, Carsten Ziegeler wrote:

> > if i edit wziml-html.xsl, the first change is noticed and applied, but any
> > changes after that are not. the string 'wziml-html.xsl' does not appear in
> > cocoon.log anywhere, so there's nothing useful there to report.
> >
> > personally, i consider this to be a show-stopper bug. no designer is going
> > to want to work on a system that requires the sysadmin to continually
> > restart tomcat to see changes.
> >
> You are absolutely right, this is a show stopper.
> But in your example above, the whole pipeline for your pattern "*" is
> not cached at all, as the aggregate component is not cacheable right
> now (it declares cacheable, but returns "null" for the CacheValidity
> object).


> According to other reports, did you try to turn off the "use-store"
> configuration of the TraxTransformer? There are some other reports,
> that after turning this off, everything works fine.

argh, i must've skipped right over that parameter dozens of times now.
yeah, if i set it to false, the problem goes away. makes sense. what
classes are responsible for the transformer store?

- donald

To unsubscribe, e-mail:
For additional commands, email:

View raw message