[Seaside-dev] Seaside 3.0.4 ... Issue 643

[Dale Henrichs]

For Issue 643, I ran into a case during GemStone testing yesterday where 
there was WAUserConfiguration with a stale cache.

WAUserConfigurations _aren't_ reachable by doing the:

   WASystemConfiguration allSubclasses do: [ :each |
     each instance clearSearchContexts.
     each instance clearDescription ].

trick. I ended up doing the following to get past the problem:

   WAFileHandler default: nil

I consider this way too harsh, since it destroys any changes that a user 
may have made to the configuration ... I think that this really means 
that we have to have a fix for Issue 643 before finishing Seaside 3.0.4 ...

In the bug report, Avi, mentions that it should be possible to do a 
second lookup that does not rely on the cache and it sounds to me that 
this is the preferable solution ...

My WAConfiguration foo is not good enough to know the right answer here. 
I just know that Seaside users might be surprised if they upgrade their 
system to Seaside 3.0.4...

Dale