Mailing-List: contact user-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@forrest.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Date: Wed, 8 Mar 2006 11:51:45 +1100
From: David Crossley <crossley@apache.org>
To: user@forrest.apache.org
Subject: Re: cache insight?
Message-ID: <20060308005145.GB3024@igg.indexgeo.com.au>
References: <440E1F2E.3010201@greenjaguar.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <440E1F2E.3010201@greenjaguar.com>
User-Agent: Mutt/1.4.2.1i

Helena Edelson wrote:
> Hi,
> I have been running into a cache issue I think.

Did you solve the previous issue that you asked
for help with. It seemed that you had a fundamental
installation issue, but you didn't say whether our
feedback helped you.

> Even if I shutdown jetty, delete the cache, run forrest clean,
> reboot my machine, restart jetty, run localhost in an new browser window
> or even a different browser program,
> changes to various xsl file I am working on are not reflected.
> Somehow Jetty or something else holds on to an older iteration of the 
> xsl file.
> This has happened lately even with changes to xml data files, something 
> was holding onto
> several iterations previous of the file's data.
> Logs say nothing indicative except:
> WARN    (2006-03-07) 18:28.40:136   [core.manager] 
> (/articles/photoessays/yosemite_sar.html)
> PoolThread-4/CoreServiceManager: disposing of handler for unreleased 
> component. role
> [org.apache.cocoon.components.treeprocessor.ProcessorComponentInfo]

I don't think that that log message is related.

-David

> Anyone have insight or solved this themselves?
> 
> helena