Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 71543 invoked by uid 500); 14 May 2002 21:06:31 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 71522 invoked from network); 14 May 2002 21:06:30 -0000 Date: Tue, 14 May 2002 23:05:42 +0200 (CEST) From: Stephan Michels To: cocoon-dev Subject: SitemapSource and validity Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi, I notice a strange behaviour of the SitemapSource, when I try to get the validity. I tested it with a pipeline with two sitemap components with are both cachable. But the SitemapSource returns null from SitemapSource.getValidity(). SitemapSource.discardValidity(): [...] String hashKey = pck.toString() + validity.toString(); this.lastModificationDate = HashUtil.hash(hashKey); // Print the last modification date System.out.println("lastModificationDate="+lastModificationDate); [...] SitemapSource.getValidity(): [...] if (this.lastModificationDate < 1) { return null; } else { return new TimeStampValidity( this.lastModificationDate ); [...] I think this is a bit dangerous, because I think hash keys could also be negative. In my case I have the following output: lastModificationDate=-5559366061692719795 source.getValidity()=null Thank you, Stephan Michels. --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org