cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Baptiste Quenot (JIRA)" <>
Subject [jira] Closed: (COCOON-1681) Generator "directory": Caching too much
Date Mon, 06 Feb 2006 11:51:04 GMT
     [ ]
Jean-Baptiste Quenot closed COCOON-1681:

    Fix Version: 2.2-dev (Current SVN)
                 2.1.9-dev (current SVN)
     Resolution: Fixed

Committed, thanks!


> Generator "directory": Caching too much
> ---------------------------------------
>          Key: COCOON-1681
>          URL:
>      Project: Cocoon
>         Type: Bug
>   Components: * Cocoon Core
>     Versions: 2.1.8, 2.1.7
>     Reporter: Antonio Fiol
>     Assignee: Jean-Baptiste Quenot
>      Fix For: 2.2-dev (Current SVN), 2.1.9-dev (current SVN)
>  Attachments:, stack1, stack2, stack3
> 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:
For more information on JIRA, see:

View raw message