[Seaside] upgrading methods

Philippe Marschall philippe.marschall at gmail.com
Fri Feb 23 07:04:23 UTC 2007


2007/2/23, Brad Fuller <brad at sonaural.com>:
> Brad Fuller wrote:
> > Lukas Renggli wrote:
> >>> >     WAComponent allSubclassesDo: [ :each | each initialize ].
> >>> >     WADispatcher resetAll.
> >>
> >> After doing this you need to stop and restart the server, so that it
> >> catches the new dispatcher.
> >>
> >>> UPDATE: Twice I stopped WAKom and restarted. The 3rd time, I stopped it,
> >>>   waited, and restarted and Seaside came up. Don't know if it was a
> >>> browser cache problem or what.
> >>>
> >>> But, I don't have my Pier app. And, I want my Pier app!
> >>
> >> Excellent, now re-initialize Pier:
> >>
> >>     PRPierFrame initialize.
> >>
> >> Answer: yes (create an entry point) - no (create a new kernel) - a
> >> Kernel (select your old kernel) - accept (suggested entry point) - ok
> >> (try in the web browser).
> >
> > Ok, another problem. I upgraded per your advice for the order. I saved
> > as new version just so I could get back to where I was.
> >
> > Seaside ran fine when updating. No problem.
> > But, when I run the new version I rcv from the browser:
> >
> > ======
> >  Internal Error
> > MessageNotUnderstood: WAStandardFiles>>urlOf:
> >
> > [] in WAStandardFiles(WAFileLibrary)>>updateRoot: {[:each | (each
> > endsWith: #Js) ifTrue: [aHtmlRoot javascript url: (sel...]}
> > Array(SequenceableCollection)>>do:
> > WAStandardFiles(WAFileLibrary)>>updateRoot:
> > WAStandardFiles>>updateRoot:
> > [] in WAApplication>>updateRoot: {[:each | each default updateRoot:
> > anHtmlRoot]}
> > OrderedCollection>>do:
> > WAApplication>>updateRoot:
> > WASession>>updateRoot:
> > WARender>>buildDocRoot
> > WARender>>buildResponse
> > [] in WARender>>render {[:u | url := u. self buildResponse]}
> > [] in WASession>>respond: {[:cc | url := self actionUrlForContinuation:
> > cc. response := responseBlock...]}
> > ResponseContinuation class(Continuation class)>>currentDo:
> > WASession>>respond:
> > WARender>>render
> > [] in WARender>>go {[self render]}
> > BlockContext>>on:do:
> > WARender>>withRenderNowHandler:
> > [] in WARender>>go {[self withRenderNowHandler: [self render]. self
> > shouldRedirect ifTrue: ...]}
> > BlockContext>>on:do:
> > ======
> >
> > If I: WADispatcher resetAll
> > I rcv DNU: WAFileHandler: #basePath
> >
> > WAFileHandler>>registerAsHandler: aString sends the message:
> >
> >   handler := self new basePath: aString.
> >
> > aString is: 'files'
> >
> > WAFileHandler is trying to initialize, but there is no #basePath
> >
> > So, I did something wrong during updating.
> >
> > Any hints????
> >
>
> Luckily I saved the image in increments. I went one back and it seems to
> work.
>
> What I merged for the last image version, that didn't work, was

Why did you merge?

> Pier-Magma
> rsrss
> Pier-Blog
>
> And, I also tried to merge FileLibrary, in this last version, but I
> could never get it to merge. When I pressed the Merge button in the
> Merge Dialog box, it just did nothing.

FileLibrary is part of Seaside since October last year and since then
has been developed inside Seaside. Merging it is not a clever idea.

Cheers
Philippe

> So, could any of these packages be the cause of the above trace?
>
> --
> brad fuller
>   http://www.Sonaural.com/
>   +1 (408) 799-6124
>
>
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>


More information about the Seaside mailing list