Hi, today I spent several hours digging through your sourcecodes ... after getting the basic idea behind it, it isn't that difficult ... but ... (either I didn't get it right or there's another problem ;) the FileWatchPortlet (which is extended by JetspeedContent) should check for changes in a local file (using org.apache.jetspeed.portal.expire.FileWatchExpire). FileWatchExpire will in turn use a FileWatcher to look for changes. FileWatcher just "remembers" the ModificationDate of the entry and compares it against the current ModificationDate of the corresponding DiskCacheEntry. I don't know, if I got the thing right up-front ... a FileWatchPortlet should expire "at the instant" a local file is modified ... not just after some diskcachedaemon-run? In this case, I seems to me, as if it wouldn't work, because the DiskCacheEntry would always return the same LastMod-Date and wouldn't check against the "correct" (i.e. the file's) LastMod-Date .... in the other case (if it should only expire after a diskcachedaemon-run) it still doesn't work for me After locally changing the getLastModified()-method of JetspeedDiskCacheEntry (just for debugging purposes) to return the current mod-date of the file on disk, after changing the .xml-file, I get the message "Portlet is set to expire ...." in the log, but I still get the stale content of the last run .... Thanks for further information, Ingo -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Search: <http://www.mail-archive.com/[email protected]/> List Help?: [EMAIL PROTECTED]
