[Seaside-dev] WAAdmin clearConfigurationCaches not working

[Johan Brichau]

Sorry about my downtime. Life has been a little crazy on me these last few months.

Option 2 is fine. We can trigger reregistration on Metacello upgrade.
I’ll try to take care of this asap (if anything is still needed?

Johan

> On 17 Dec 2014, at 14:59, Philippe Marschall <philippe.marschall at gmail.com> wrote:
> 
> On Mon, Sep 1, 2014 at 3:55 PM, 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.
> 
> *bump*
> 
> Cheers
> Philippe
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev