[Seaside-dev] Issue 140 in seaside: decide whether WAObject>>session and >>application should return nil if no request context found

[codesite-noreply at google.com]

Issue 140: decide whether WAObject>>session and >>application should return  
nil if no request context found
http://code.google.com/p/seaside/issues/detail?id=140

Comment #6 by jfitzell:
I fixed the problem for the Debugger by having the error handler catch the
WARequestContextNotFound error and resume with a stored value. But  
obviously this
wouldn't help with inspectors...

I wonder how often this is likely to be a problem (things needing the  
requestContext
to display themselves in the inspector). We could provided  
#requestContextOrNil,
which catches the error and returns nil but if all the code ends up using  
that then
we'd be back where we started and the Debugger wouldn't work anymore  
because the
error wouldn't be getting propagated far enough for the error handler to  
resume it.

I'd still favour having the error unless someone can show a whole bunch of  
cases
where it will be a problem for inspecting. I'd probably be easily convinced  
if so.



-- 
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings