Carsten Ziegeler wrote:
Ok, I thought I read somewhere that this had been fixed. Anyways, yes, contacting them is the better way.No, I believe it was an NPE on shutdown, or something like that - not very graceful.
We'll see how they reply.
I'd say it probably is a showstopper, but I'm not sure how much people rely upon the survival of the cache over shutdowns.
The other option is to release with JISP, and fix straight after release, maybe then do a quick 2.1.6. After all, the JISP problems have been in releases already, so they're not quite showstoppers in the same way.
Otherwise we're in danger of loosing our release often, release early maxim. Right here is where loosing that begins!!!
Regards, Upayavira
-----Original Message-----
From: Upayavira [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 18, 2004 9:47 AM
To: [EMAIL PROTECTED]
Subject: Re: Testing the cache implementation....
Carsten Ziegeler wrote:
Good,
but unfortunately the data does not survive a Cocoon restart on my system. Any idea?
I don't believe it is supposed to.
I've just joined jcs-dev and asked whether they'll add it! They seem responsive enough.
Regards, Upayavira
index with-----Original Message----- From: Antonio Gallardo [mailto:[EMAIL PROTECTED] Sent: Monday, May 17, 2004 6:04 PM To: [EMAIL PROTECTED] Subject: Testing the cache implementation....
Hi:
I already did the following test: started lucene building
remember thattransformer then on another client I sent to clear the cache. The cache was cleared and on the jetty console no error. I
caused a problem in 2.1.4
If this is true, then it is a point for JCS. :-D
Best Regards,
Antonio Gallardo.
