Seaside 3 in VisualWorks 7.7

> Hi,
>
> I am using visualworks 7.7 and the bundled seaside version (3.0).
> Differently from the version in visualworks 7.6, in any web application
> I build with seaside, the session expires each time I press refresh
> in the browser.
>
> Is it an intended behavior? Could it be possible to change it,
> and restore the old one?
>    

> Hi,
>
> I am using visualworks 7.7 and the bundled seaside version (3.0).
> Differently from the version in visualworks 7.6, in any web application
> I build with seaside, the session expires each time I press refresh
> in the browser.
>
> Is it an intended behavior? Could it be possible to change it,
> and restore the old one?
>
> Thanks,
> Alberto
>
> PS I apologize for the cross posting,
> but I am not sure about the most appropriate mailing list
> to use in this case.
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>

> 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
> way:
>        MySession>>new
>                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.
>
> Cheers,
> Alberto
>
> 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.
>>
>> Julian
>
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>

>
> 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.
>
> http://code.google.com/p/seaside/issues/detail?id=364
>
> 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).
>
> Julian

> On 3/10/10 9:38 AM, Alberto Bacchelli wrote:
>> Hi,
>>
>> I am using visualworks 7.7 and the bundled seaside version (3.0).
>> Differently from the version in visualworks 7.6, in any web application
>> I build with seaside, the session expires each time I press refresh
>> in the browser.
>>
>> Is it an intended behavior? Could it be possible to change it,
>> and restore the old one?
>>
> Seaside 3.0 in VW7.7 is an alpha version, so you're best bet is to bring
> it up on the seaside mailing list. It sounds like a bug but without more
> details I couldn't really comment.