Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Date: 19 Jan 2003 16:07:44 -0000
Message-ID: <20030119160744.20334.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: cocoon-dev@xml.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 16240] New:  -
    caching issue,
 improper calculation of last modification date in SitemapSource.java

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16240>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16240

caching issue, improper calculation of last modification date in SitemapSource.java

           Summary: caching issue, improper calculation of last modification
                    date in SitemapSource.java
           Product: Cocoon 2
           Version: 2.0.4
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: core
        AssignedTo: cocoon-dev@xml.apache.org
        ReportedBy: m_rolappe@web.de


the problem is the following code in method refresh() in SitemapSource.java:

...
    if (validity != null) {
    // the event pipeline is cacheable
    // now calculate a last modification date
    String hashKey = pck.toString() + validity.toString();
    this.lastModificationDate = HashUtil.hash(hashKey);
    }
...

more specifically, the hashkey is the problem; it's the concatenation of all 
the validities' toString() strings, which can differ between calls (in my case 
DeltaTimeCacheValidity).

this leads to the respective pipeline not being cached although the 
CachedEventPipeline validity itself is valid.

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org