On Tue, Jan 11, 2005 at 12:06:46PM +0100, Erik Bruchez wrote: > There have been some fixing made to caching for 2.7 for some particular > processors (Request generator, Scope generator, URL generator, mainly), > and there is now also a unit test suite for testing the caching behavior > of several processors, so it is definitely worth upgrading. But still, I > have never experienced a behavior as broken as the one you are > describing. Not saying it does not happen in your case, but I am > wondering what kind of setup could cause this.
I installed a clean 2.7.1 and installed my test application in that tree and I now have it working like in the old situation. Nothing changed w.r.t. the file caching problem (nor the long URI problem). W.r.t. the file caching problem I see the following behavior: - When I change a file short after each other (say, within 10 sec or so), the change is in most cases not seen, and this stays the same (forever?) until I change (the timestamp of) the file again or restart Tomcat. - When there is a longer period between the changes, the change is in most cases (but not always) seen immediately. > Do you access your resources through the FlatFileResourceManager, or > through another resource manager? I use the stock 2.7.1 web.xml, where FlatFileResourceManager is commented out. -- -- Jos Vos <[EMAIL PROTECTED]> -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 -- Amsterdam, The Netherlands | Fax: +31 20 6948204 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ orbeon-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/orbeon-user
