Re: XSP in XSL and Caching problem!
Timothy and others, I think I found a solution to this problem! By adding this: xsp:dependency/some/file/here.xsl/xsp:dependency Into the XSP file, ServerPagesGenerator checks if that file has also changed. If it is, the XSP is recompiled. You can add as many dependencies as you want. See: src\java\org\apache\cocoon\components\language\markup\xsp\java\xsp.xsp for more on this. I haven't tested with a relative path yet, but it should work too. After you add those lines, you have to remove the work dir, and restart tomcat one more time. Of course, this is manual a trick, and SHOULD be totally automatic in Cocoon with it's otherwise great caching algorithms. I've reported the bug in Bugzilla. -Tuomo - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: XSP in XSL and Caching problem!
We really need some advice on this problem. It's slowing our development by 600% ! Anyone? Cocoon 2.1-DEV (from CVS about a month ago) Tomcat 4.0.5 JDK 1.4.1_01 On Thu, 10 Oct 2002, Timothy Larson wrote: I am having the same problem and am using the same ugly workaround. Tomcat 3.3.1 Cocoon 2.0.4dev (from CVS around 9-17-2002) JDK 1.4.0_02 If I serialize the XSP page as XML it is always is up-to-date, but when I use the XSP as a serverpage it is usually out-of-date. This tells me that the XML of the XSP page is being cached properly, but the JAVA code that it generates is not being updated at the same time. On rare occasions it will update with changes to the XSL page that generates it, but most of the time I have to take down Tomcat and clear the work directory to get the code generated from the XSP to update. Tim [EMAIL PROTECTED] 10/10/02 10:52AM I'm using 2.1-DEV, and one file in my application is a XSL page which generates XSP for the serverpagesGenerator. The problem here is, that no changes are committed to the browser result! Only removing the work-dir and restarting tomcat helps. And after one reload of that page it's still the same. I've changed all the pipelines to noncaching, and everything is set to false that seems like a caching instruction. I've tryed IE6, and NN7, no difference. Help, please! -Tuomo - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
XSP in XSL and Caching problem!
I'm using 2.1-DEV, and one file in my application is a XSL page which generates XSP for the serverpagesGenerator. The problem here is, that no changes are committed to the browser result! Only removing the work-dir and restarting tomcat helps. And after one reload of that page it's still the same. I've changed all the pipelines to noncaching, and everything is set to false that seems like a caching instruction. I've tryed IE6, and NN7, no difference. Help, please! -Tuomo - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: XSP in XSL and Caching problem!
- Original Message - From: Tuomo Lesonen [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, October 10, 2002 3:52 PM Subject: XSP in XSL and Caching problem! I'm using 2.1-DEV, and one file in my application is a XSL page which generates XSP for the serverpagesGenerator. The problem here is, that no changes are committed to the browser result! Only removing the work-dir and restarting tomcat helps. And after one reload of that page it's still the same. I've changed all the pipelines to noncaching, and everything is set to false that seems like a caching instruction. I've tryed IE6, and NN7, no difference. Help, please! -Tuomo Hello ! I´m having the same problem here ... My setup is Tomcat 4.1.12 Cocoon 2.0.3 JDK 1.4.0 I've been extending some examples like the bonebreaker site (http://www.cocooncenter.de/cc/documents/resources/navigation/index.html) just to avaliate Cocoon for some internal company work, and i must say the reload/refresh problem is screwing my devel process. (in this particular case, if some info on toc.xml is modified, tomcat work dir must be cleaned and the server restarted). Might this be a tomcat-cocoon right/wrong version problem ? Any help? :) Thanks in advance... [--] Rui Pedro Leal [--] [EMAIL PROTECTED] [--] [EMAIL PROTECTED] [--] ICQ: 318173 - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: XSP in XSL and Caching problem!
I am having the same problem and am using the same ugly workaround. Tomcat 3.3.1 Cocoon 2.0.4dev (from CVS around 9-17-2002) JDK 1.4.0_02 If I serialize the XSP page as XML it is always is up-to-date, but when I use the XSP as a serverpage it is usually out-of-date. This tells me that the XML of the XSP page is being cached properly, but the JAVA code that it generates is not being updated at the same time. On rare occasions it will update with changes to the XSL page that generates it, but most of the time I have to take down Tomcat and clear the work directory to get the code generated from the XSP to update. Tim [EMAIL PROTECTED] 10/10/02 10:52AM I'm using 2.1-DEV, and one file in my application is a XSL page which generates XSP for the serverpagesGenerator. The problem here is, that no changes are committed to the browser result! Only removing the work-dir and restarting tomcat helps. And after one reload of that page it's still the same. I've changed all the pipelines to noncaching, and everything is set to false that seems like a caching instruction. I've tryed IE6, and NN7, no difference. Help, please! -Tuomo - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Please check that your question has not already been answered in the FAQ before posting. http://xml.apache.org/cocoon/faq/index.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
