RE: XSPClassLoader: Caching problem in Cocoon 1.8 once page is su cces sfully compiled.

[Michael Hussey <MH...@Saba.com>]

Yes, I meant the classes are not loaded into memory, even though the class
files are updated.  Thanks for pointing out the TODO file.  It sounds like
exactly our problem.

We have had to fix the caching problems and stylesheet chaining problems so
I'm excited to hear that you are planning on getting these addressed on the
main line.

We've also added considerable debugging support which consists of generating
xml files with intermediate results of logicsheet translations, XSP output,
and XSL transforms, as well as displaying this XML in the browser.  We'd
love to have this functionality rolled into the main line.  Let me know if
you would like to see the code for possible inclusion.

Thanks for your support,
Michael

-----Original Message-----
From: Robin Green [mailto:greenrd@hotmail.com]
Sent: Saturday, November 04, 2000 3:15 PM
To: cocoon-dev@xml.apache.org
Subject: Re: XSPClassLoader: Caching problem in Cocoon 1.8 once page is
succes sfully compiled.


Michael Hussey <MH...@Saba.com> wrote:
>We have found that our compiled pages are not updated even after the source
>is updated.

The source for what? XSP pages or associated classes? If you mean associated

classes, this is a known bug, listed in "To Do". As I noted in the "To Do" 
file, I have already fixed this problem (no cache is needed), I just have to

merge my changes into the trunk and document them.

If you mean XSP pages, I am perplexed - in that case please give full 
configuration details of your system (OS, JDK, servlet engine, Cocoon 
version). Also have you checked the FAQ on pages not recompiling?



_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

Share information about yourself, create your own public profile at 
http://profiles.msn.com.