Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 25701 invoked from network); 8 Feb 2004 08:48:50 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 8 Feb 2004 08:48:50 -0000 Received: (qmail 77744 invoked by uid 500); 8 Feb 2004 08:48:23 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 77503 invoked by uid 500); 8 Feb 2004 08:48:21 -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 77471 invoked from network); 8 Feb 2004 08:48:20 -0000 Received: from unknown (HELO confixx.bestiole.ch) (66.111.0.243) by daedalus.apache.org with SMTP; 8 Feb 2004 08:48:20 -0000 Received: from apache.org (lsn-boi-catv-c121-p001.vtx.ch [212.147.121.1]) by confixx.bestiole.ch (8.11.6/8.11.6) with ESMTP id i188mVP14460 for ; Sun, 8 Feb 2004 09:48:31 +0100 Date: Sun, 8 Feb 2004 09:48:48 +0100 Subject: Re: DO NOT REPLY [Bug 26753] - Persistent store or cache corruption? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Mime-Version: 1.0 (Apple Message framework v553) From: Bertrand Delacretaz To: dev@cocoon.apache.org Content-Transfer-Encoding: quoted-printable In-Reply-To: <40256A63.3010005@leverageweb.com> Message-Id: <9C74DA5A-5A13-11D8-862C-000393CFE402@apache.org> X-Mailer: Apple Mail (2.553) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Le Samedi, 7 f=E9v 2004, =E0 23:44 Europe/Zurich, Geoff Howard a =E9crit = : > bugzilla@apache.org wrote: > > > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3D26753 >> Persistent store or cache corruption? >> ------- Additional Comments =46rom cziegeler@apache.org 2004-02-07=20= >> 18:34 ------- >> Afaik, this is a known Jisp bug which should be fixed according to=20 >> Scott with Jisp 3.0. We could try to switch to Jisp 3.0 after the=20 >> release and see what happens. > > Are you saying after the release because Jisp 3.0 would require more=20= > changes in the excalibur/cocoon code? =46rom what I read about this=20= > bug, I'd say it's important enough to try to fix it before the release=20= > if at all possible, no? Releasing with this bug worries me as well. In my tests I've seen=20 either garbage or wrong pages (ie another page than the one I did=20 request) being served, this is a serious problem. The Cocoon core is known to be very stable and reliable, we don't want=20= to give a bad impression here IMHO. I'd consider it a blocker and=20 would vote against the release unless there is at least a workaround. -Bertrand