[Seaside] Hook "WACurrentRequestContext" into debugger?

Mariano Martinez Peck marianopeck at gmail.com
Thu Dec 3 23:34:57 UTC 2015

Hi guys,

This thing I will ask in this email it's in my mind since YEARS. But I have
always thought it was like that and that there was nothing we could do.
However, I think it's time I ask again :)

For those that have used Seaside, and you try to debug, you know that upon
request processing seaside uses Exceptions mechanisim to always have access
to the request, session, etc. They way that is done is very smart :)

 WACurrentRequestContext use: self during: aBlock

In that case, "self" is the request instance and aBlock the closure that
takes care of the request processing. So, inside that closure, everywhere
you do "WACurrentRequestContext value" you get the correct request instance.

So..that's great for Seaside, but debugging gets complicated. While you can
restart, proceed, etc, once inside debugger, you  cannot evaluate any piece
of code that will use the session  or request because you get
a WARequestContextNotFound. Of course, because I guess the evaluation you
do from cmd+d on a piece of text or via the debugger inspector, creates
another closure/context which does not receive the WACurrentRequestContext

Now....besides WACurrentRequestContext I have my own class
UserContextInformation where I basically have a bunch of stuff associated
to the logged user. And I do exactly the same as the
WACurrentRequestContext. And I have the same problem. I really want to be
able to fix this.

Anyone have an idea on how can I do it? I guess I can change the debugger,
in the place where I evaluate code so that I wrap that evaluation with my
request context instance???


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20151203/9cfea791/attachment.htm

More information about the seaside mailing list