Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 33776 invoked by uid 500); 9 May 2001 06:48:31 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 33761 invoked from network); 9 May 2001 06:48:29 -0000 From: "Carsten Ziegeler" To: Subject: AW: [c2] still having caching problems Date: Wed, 9 May 2001 08:48:12 +0200 Message-ID: MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-MIMETrack: Itemize by SMTP Server on PBSN1/Systeme und Netzwerke(Release 5.0.5 |September 22, 2000) at 09.05.2001 08:48:09, Serialize by Router on PBSN1/Systeme und Netzwerke(Release 5.0.5 |September 22, 2000) at 09.05.2001 08:48:10, Serialize complete at 09.05.2001 08:48:10 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii" X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > Donald Ball wrote: > > 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). > > okay. > > > 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? > As far as I know, the TraxTransformer, the used Store and some Xalan classes. But I think the main logic is in the TraxTransformer itself. Carsten > - donald > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org > For additional commands, email: cocoon-dev-help@xml.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org