[Seaside-dev] Issue 69 in seaside: printOn: a WAUrlEncoder can get interesting when no WACurrentContext on stack

[codesite-noreply at google.com]

Issue 69: printOn: a WAUrlEncoder can get interesting when no 
WACurrentContext on stack
http://code.google.com/p/seaside/issues/detail?id=69

Comment #1 by philippe.marschall:
The issue is probably in WAUrlEncoder >> #initializeOn:table: . The 
question is what
do we do if we know that there is no request context. Either raise an 
error or use a
NullCodec. I'd rather raise an error.



-- 
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