Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 11938 invoked from network); 14 May 2004 16:14:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 14 May 2004 16:14:17 -0000 Received: (qmail 71177 invoked by uid 500); 14 May 2004 16:14:26 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 71098 invoked by uid 500); 14 May 2004 16:14:25 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 71057 invoked by uid 98); 14 May 2004 16:14:24 -0000 Received: from anonymous@nagoya.betaversion.org by hermes.apache.org by uid 82 with qmail-scanner-1.20 (clamuko: 0.70. Clear:RC:0(192.18.33.10):. Processed in 0.052492 secs); 14 May 2004 16:14:24 -0000 X-Qmail-Scanner-Mail-From: anonymous@nagoya.betaversion.org via hermes.apache.org X-Qmail-Scanner: 1.20 (Clear:RC:0(192.18.33.10):. Processed in 0.052492 secs) Received: from unknown (HELO exchange.sun.com) (192.18.33.10) by hermes.apache.org with SMTP; 14 May 2004 16:14:24 -0000 Received: (qmail 28646 invoked by uid 50); 14 May 2004 16:15:04 -0000 Date: 14 May 2004 16:15:04 -0000 Message-ID: <20040514161504.28645.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: dev@cocoon.apache.org Cc: Subject: DO NOT REPLY [Bug 28724] - FragmentExtractor always returns same fragment X-Spam-Rating: hermes.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=28724 FragmentExtractor always returns same fragment ------- Additional Comments From sarah.windler@id.ethz.ch 2004-05-14 16:15 ------- More tests: I wrote the class not cacheable: 1. Commented out the Interface CacheabelProcessingComponent -> same effect 2. getValidity(), return value: null for no cacheable -- same effect. It seems to be a bug outside of this class? Sarah