[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

New issue report by da... at teleport.com:

1. put a halt in WAUrlTest>>testParseAmbiguous as follows:
testParseAmbigous
	self ambigousExamples do: [ :each |
		self
			assert: (WAUrl halt absolute: each first) toString = each last
		 	description: each last resumable: true ]

2. run the test and step into WAUrl>>initializeFromString:
3. After stepping over 'self initialize', select self and you'll get an
error, because there is no WACurrentRequest on the stack .... '<error in
printString: evaluate "self printString" to debug>'...

Presumably the folks that use WACurrentRequest to get values should do nil
checks to avoid getting such errors ...




Issue attributes:
	Status: Accepted
	Owner: da... at teleport.com
	Labels: Type-Defect Priority-Medium Version-Seaside2.9 Platform-Squeak

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