[Seaside-dev] Global Seaside re-initialization

[Johan Brichau]

Esteban,

I don’t know if this would be specific to VW, but it sounds like you need to reregister the applications.
See “Upgrading” and “Breaking changes” in the release notes for 3.2.0:

https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog <https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog>

Let us know if there is something different going on
Johan

> On 26 May 2017, at 16:48, Esteban A. Maringolo <emaringolo at gmail.com> wrote:
> 
> Hi all,
> 
> I loaded Seaside 3.2 on top of the previously loaded 3.1 in VW and now
> everytime I try to access an application I'm getting errors of the
> kind of the one in the following stack:
> 
> Message not understood: #keyFromContext:
> Seaside.WAQueryFieldHandlerTrackingStrategy class(Object)>>doesNotUnderstand:
> Seaside.WAApplication(Seaside.WARegistry)>>handleFiltered:
> Seaside.WAApplication>>handleFiltered:
> Seaside.WAExceptionFilter(Seaside.WARequestFilter)>>handleFiltered:
> optimized [] in [] in Seaside.WAExceptionFilter>>handleFiltered:
> BlockClosure>>on:do:
> 
> For some reason the configuration is returning the class of the
> tracking strategy instead of an instance.
> 
> I could create a new image from scratch, but I'd like to know how to
> reset everything, since most initializations are automatically
> executed by class side #initialize method.
> 
> Regards!
> 
> Esteban A. Maringolo
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20170526/9871824a/attachment-0001.html>