[Seaside-dev] Issue 189 in seaside: WADispatcherTest should not depend on the default environment

[codesite-noreply at google.com]

Issue 189: WADispatcherTest should not depend on the default environment
http://code.google.com/p/seaside/issues/detail?id=189

Comment #1 by jfitzell:
Name: Seaside-Tests-Core-jf.9
Author: jf
Time: 7 October 2008, 2:04:18 am
UUID: b22ed7fb-8d58-534d-8329-9c35e1b8bd43
Ancestors: Seaside-Tests-Core-jf.8

Name: Seaside-Tests-Session-jf.2
Author: jf
Time: 7 October 2008, 2:04:51 am
UUID: a00d73c7-7d67-4d4b-a202-d21c7d032f25
Ancestors: Seaside-Tests-Session-jf.1

Name: Seaside-Tests-Environment-jf.2
Author: jf
Time: 7 October 2008, 2:04:36 am
UUID: 4e363505-dcb2-d843-a457-9564ecd2d43c
Ancestors: Seaside-Tests-Environment-jf.1

Name: Seaside-Tests-Development-jf.8
Author: jf
Time: 7 October 2008, 2:05:32 am
UUID: 2aa05f92-d248-694f-8765-50b9dbecb6cb
Ancestors: Seaside-Tests-Development-jf.7

Name: Seaside-Tests-Squeak-Kom-jf.3
Author: jf
Time: 7 October 2008, 2:05:07 am
UUID: 14a531b3-36c2-784a-bc24-8b36ac2320eb
Ancestors: Seaside-Tests-Squeak-Kom-jf.1

+ Rename existing WADocumentHandlerTest to WADocumentHandlerResponseTest
+ Rename WAKomDocumentHandlerTest to WAKomDocumentHandlerResponseTest
+ Move some of WADispatcherTest to new WAEnvironmentDefaultHandlersTest
+ Delete or rewrite the rest of WADispatcherTest in a new hierarchy of test  
cases,
starting with WARequestHandlerTest and covering each subclass





Name: Seaside-Core-jf.276
Author: jf
Time: 7 October 2008, 1:55:36 am
UUID: cb17d1cc-39f7-024d-82a2-3f106506a9e5
Ancestors: Seaside-Core-jf.275

Implement accessors and #postCopy on WADocumentHandler to make new tests  
pass.

Also implement WAMimeDocument>>= and update class comment on WARegistry.



Name: Seaside-Development-jf.4
Author: jf
Time: 7 October 2008, 1:59:33 am
UUID: cdde523a-8008-c645-a37b-7ddde6e90970
Ancestors: Seaside-Development-jf.3

Name: Seaside-Tests-Development-jf.8
Author: jf
Time: 7 October 2008, 2:05:32 am
UUID: 2aa05f92-d248-694f-8765-50b9dbecb6cb
Ancestors: Seaside-Tests-Development-jf.7

Implement #cloneHandler on the RequestHandler hierarchy and use it in
WACopyDispatcherPlugin.

For most request handlers we just want to #copy, but for Applications we  
want to make
sure we then clear the cache. Otherwise we'd have a copy that had all the  
same
sessions in it. Eww...

This was based on my assumption that in the general case of WAEntryPoint,  
we don't
necessarily want to clear the cache in #postCopy. Somebody might have an  
EntryPoint
subclass that they want to copy in some context and still have the  
registered request
handlers in the cache. If this assumption is wrong, WAEntryPoint>>postCopy  
could be
adjusted and this version reverted.





Issue attribute updates:
	Status: Fixed
	Owner: jfitzell

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