Global Seaside re-initialization
Locked
Global Seaside re-initialization
 
|
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 [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
|
|
Try this:
WAAdmin clearAll. WAConfiguration allSubInstancesDo: #clearSearchContexts. WASystemConfiguration allSubInstancesDo: #clearDescription. (#clearAll does not correctly reset descriptions) Max > On 26 May 2017, at 16:48, Esteban A. Maringolo <[hidden email]> 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 > [hidden email] > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev _______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
Re: Global Seaside re-initialization
|
|
In reply to this post by Esteban A. Maringolo
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: Let us know if there is something different going on Johan
_______________________________________________ seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
Re: Global Seaside re-initialization
|
|
Hi Johan,
I followed the recommended procedure in the wiki page and found what was causing the issue, the server adapter was referencing an old,dangling, instance of the default WADispatcher. I set it to nil and everything started working ok. WAAdmin clearAll. WAConfiguration allSubInstancesDo: #clearSearchContexts. WASystemConfiguration allSubInstancesDo: #clearDescription. WAServerManager default stopAll. WAServerManager instVarNamed: 'default' put: nil. SeasideResponder defaultSeasideRequestDispatcher: nil. WAEnvironment reloadApplications. Also, I don't know if it is a bug or a feature, but WAServerManager class>>#default is accessing the default instance variable, that in my previous attemps, was nil. Shouldn't it check for nil before accessing its contents? WAServerManager class>>#default default isNil ifTrue: [self initializeDefaultValueHolder]. "<-- add this?" default contents ifNil: [ default contents: self new ]. ^ default contents Thank you very much, Esteban A. Maringolo 2017-05-26 11:52 GMT-03:00 Johan Brichau <[hidden email]>: > 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 > > Let us know if there is something different going on > Johan > > On 26 May 2017, at 16:48, Esteban A. Maringolo <[hidden email]> 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 > [hidden email] > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev > > > > _______________________________________________ > seaside-dev mailing list > [hidden email] > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev > seaside-dev mailing list [hidden email] http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev |
«
Return to Seaside Development
|
1 view|%1 views
| Free forum by Nabble | Edit this page |