[Seaside] Seaside 3 in VisualWorks 7.7
jfitzell at gmail.com
Wed Mar 10 22:11:32 UTC 2010
Oh, hang on. If you haven't clicked on a link, then yes, this is
normal (if not always desired) behaviour. The only way to avoid this
is to redirect as the very first action when starting a session. Many
people don't want this because it adds a redirect and results in the
session key being in the location bar if someone decides to bookmark
the initial page.
You can get around this by calling "self requestContext redirect"
somewhere like your root component's #initialRequest: method (I think
that should work there... untested).
On Wed, Mar 10, 2010 at 10:44 PM, Alberto Bacchelli
<alberto.bacchelli at usi.ch> wrote:
> Thanks Julian,
> in the meantime I detail how I found the issue so it will be easier to
> detect the problem.
> - Using vw 7.7 I loaded the seaside parcel shipped with visualworks (I also
> tried with the last version of seaside in the cincom store experiencing the
> same problem)
> - I subclassed WASession with MySession and override #new in the following
> Transcript show: 'new session' ; cr.
> ^super new
> - I set my application to use MySession instead of WASession
> With the above configuration, when I refresh the page I get 'new session' on
> the transcript.
> On 3/10/10 9:55 PM, Julian Fitzell wrote:
>> Hi Alberto,
>> Certainly not an intended behaviour. :) The cross-posting is fine.
>> I haven't heard any similar reports so let's see if anyone can
>> identify it as VW-specific and, if not, we'll have to dig further into
>> your setup to see if we can isolate the problem.
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside