Re: [Pharo-project] [Seaside] Problem with announcements in Seaside when using Pharo 1.3
The issue described by Andrei seems to happen only in the context of an announcement. The on:fork: fixes proposed by Igor and Stef plus overriding DynamicVariable>>alwaysResuming, seem to solve the problem. Btw, how can we get the new implementation of on:fork:? It would be cool to get someone else to test them. Cheers, Doru On 17 Jul 2011, at 21:06, Philippe Marschall wrote:
2011/7/17 Lukas Renggli <renggli@gmail.com>:
Not sure why the request context is suddenly gone in your code.
It could be that this has something to do with the announcements, the implementation changed drastically in Pharo 1.3. I had to revert the announcements to the original implementation in OB to make them work.
Do you properly receive the request context before doing the announcement, just to rule out any problems in Seaside? Seaside has not really been tested on Pharo 1.3 yet, our builds are all based on stable Pharo 1.2.1.
I've been using Pharo 1.3 for some time now and it seem to work so far.
Cheers Philippe _______________________________________________ seaside mailing list seaside@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-- www.tudorgirba.com "If you interrupt the barber while he is cutting your hair, you will end up with a messy haircut."
The on:fork: fixes proposed by Igor and Stef plus overriding DynamicVariable>>alwaysResuming, seem to solve the problem.
No, that doesn't solve the problem. People throw exceptions (not just notifications) and they expect that their handlers are able to catch them. Furthermore, it is an obscure counterpart of #isResumable (i don't understand the difference). Lukas -- Lukas Renggli www.lukas-renggli.ch
participants (2)
-
Lukas Renggli -
Tudor Girba