[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 #3 by da... at teleport.com:
Preventing an error during printOn: would be the first order of business,  
being able
to get a meaningful printString during debugging/inspecting is secondary,  
but still
pretty useful ... as it is you have to inspect the WAUrl and reconstruct  
the url
string from it's pieces, so a null codec would be more useful than not ...  
another
argument for including a codec in the core



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