[ http://issues.apache.org/jira/browse/COCOON-1681?page=comments#action_12363884 ]
Antonio Fiol commented on COCOON-1681: -------------------------------------- Still an issue on 2.1.8, and still an issue in our project. We are testing --we started this week-- a patch doing exactly what is said in the description (one line removal). So far, it is working for us. Maybe it is not the most efficient solution, but has not shown performance problems either (in some parts of the project, we work with depth=6, with quite a lot of files and directories). Please bear with our long times. I hope I will confirm our results by the end of this week. > Generator "directory": Caching too much > --------------------------------------- > > Key: COCOON-1681 > URL: http://issues.apache.org/jira/browse/COCOON-1681 > Project: Cocoon > Type: Bug > Components: * Cocoon Core > Versions: 2.1.8, 2.1.7 > Reporter: Antonio Fiol > Assignee: Cocoon Developers Team > > In some cases, an update to the directory is not detected by the > DirectoryGenerator. > Debugging the issue, I discovered that isValid() is called twice on the same > DirValidity, but it returns different values (-1 the first time, 1 the second > time). > Apparently, the reason for the inconsistency would be solved by removing the > first of the two lines that update the expiry time in the isValid() method in > DirValidity, but I am not sure whether this could cause problems in other > places. > A possibility would be that a DirValidity stores the fact that it already > detected it is invalid, and is changed so that it always return -1. But... > Are DirValidity objects reused? Could this change cause problems? I have not > tested, so I don't know. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
