Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 10615 invoked from network); 8 Nov 2000 01:49:27 -0000 Received: from nat.saba.com (HELO SABAHQMAIL.saba.com) (208.197.163.94) by locus.apache.org with SMTP; 8 Nov 2000 01:49:27 -0000 Received: by sabahqmail.saba.com with Internet Mail Service (5.5.2650.21) id ; Tue, 7 Nov 2000 17:53:55 -0800 Message-ID: From: Michael Hussey To: "'cocoon-dev@xml.apache.org'" Subject: RE: XSPClassLoader: Caching problem in Cocoon 1.8 once page is su cces sfully compiled. Date: Tue, 7 Nov 2000 17:53:48 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C04926.C005D860" X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C04926.C005D860 Content-Type: text/plain; charset="iso-8859-1" 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 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. ------_=_NextPart_001_01C04926.C005D860 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: XSPClassLoader: Caching problem in Cocoon 1.8 once page is = succes sfully compiled.

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 <MHussey@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.

------_=_NextPart_001_01C04926.C005D860--