Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 59611 invoked from network); 18 Jun 2010 18:43:58 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 18 Jun 2010 18:43:58 -0000 Received: (qmail 37350 invoked by uid 500); 18 Jun 2010 18:43:58 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 37236 invoked by uid 500); 18 Jun 2010 18:43:57 -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 37229 invoked by uid 99); 18 Jun 2010 18:43:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Jun 2010 18:43:56 +0000 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=RCVD_IN_BL_SPAMCOP_NET,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [88.198.46.98] (HELO indoqa.com) (88.198.46.98) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Jun 2010 18:43:48 +0000 Received: from [192.168.7.5] (85-126-236-147.static.xdsl-line.inode.at [85.126.236.147]) by indoqa.com (Postfix) with ESMTP id 2444C1A0001 for ; Fri, 18 Jun 2010 20:43:27 +0200 (CEST) Message-ID: <4C1BBE4D.20608@indoqa.com> Date: Fri, 18 Jun 2010 20:43:25 +0200 From: Steven Dolg User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: users@cocoon.apache.org Subject: Re: [C3] How to prevent caching a stylesheet? References: <4C1764F5.68EF.00C9.1@gmx.at> <80D67DDF46E64713B1AE7BCE182BA88D@sparksc2> In-Reply-To: <80D67DDF46E64713B1AE7BCE182BA88D@sparksc2> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi, no, there is no further caching setting you could use and there should be no caching with the configuration you described. However, after looking at some code I found this in the XSLTTransformer: private void loadXSLT(final URL source, final Map attributes) { if (source == null) { throw new IllegalArgumentException("The parameter 'source' mustn't be null."); } this.source = source; // check the XSLT is in the cache first if (XSLT_CACHE.containsKey(source)) { // get the XSLT directly from the cache this.templates = XSLT_CACHE.get(this.source); } else { ... I'm not really up-to-date but it looks like there is no way to affect this behaviour in any way. So sadly this appears to be a genuine deficiency in trunk (which been there since at least early January). I'm afraid there is no solution for this readily available (except the obvious restart) Steven Hugh Sparks schrieb: > The following pipeline (I think) is configured to be > noncaching, but editing the stylesheet.xsl file has > no visible effect when the browser page is refreshed > (and the browser cache is cleared.) > > > > > > > > > > ... > ... > > I'm using tomcat with all context "out of the jar". > > Is there some other "noncaching" thing I should specify > so changes to the stylesheet become visible without > reloading the spring context? > > Thanks! > > -Hugh Sparks > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org