[Seaside-dev] Re: WAAdmin clearConfigurationCaches not working

[Johan Brichau]

I will take a look tomorrow if I can find anything.
It has annoyed me frequently too but I got used to "bike around it" :)

I have a couple of other loose ends to fix before I would release 3.2 (ie jquery) but it will not be long.

I have defined 3.1.2 in the meantime but mind we have the failing WABrowser test.

Johan

Sent from my iPad (oh yes, still waiting for my new laptop)

> On 01 Sep 2014, at 15:55, Philippe Marschall <philippe.marschall at gmail.com> wrote:
> 
> On Sat, Aug 23, 2014 at 5:15 PM, Philippe Marschall
> <philippe.marschall at gmail.com> wrote:
>> Hi
>> 
>> As part of fixing Issue 820 [1] I have to change some configurations.
>> I though that if I do
>> 
>> WAAdmin clearConfigurationCaches
>> 
>> all the configuration caches should be cleared. However that is not
>> what is happening. #preferenceAt: in WAApplication instances still
>> return the old value.
> 
> *bump*
> 
> I see three possible ways forward:
> 1. exclude Issue 820 from 3.2 and postpone it to 3.3
> 2. include Issue 820 as is in 3.2 and require everybody to to
> reregister their request handlers
> 3. delay 3.2 until somebody fixes the issue
> 
> Opinions? I am split between 1 and 2, mostly because I don't know how
> big of a headache the current situation is on GemStone/S.
> 
> Cheers
> Philippe
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev