[EMAIL PROTECTED] wrote:
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26753Persistent store or cache corruption?
------- Additional Comments From [EMAIL PROTECTED] 2004-02-07 18:34 -------
Afaik, this is a known Jisp bug which should be fixed according to Scott with Jisp 3.0. We could try to switch to Jisp 3.0 after the release and see what happens.
Are you saying after the release because Jisp 3.0 would require more changes in the excalibur/cocoon code? From what I read about this bug, I'd say it's important enough to try to fix it before the release if at all possible, no?
Releasing with this bug worries me as well. In my tests I've seen either garbage or wrong pages (ie another page than the one I did request) being served, this is a serious problem.
The Cocoon core is known to be very stable and reliable, we don't want to give a bad impression here IMHO. I'd consider it a blocker and would vote against the release unless there is at least a workaround.
-Bertrand
