[Seaside-dev] Issue 178 in seaside: WACache / WARegsitry copying

[codesite-noreply at google.com]

Issue 178: WACache / WARegsitry copying
http://code.google.com/p/seaside/issues/detail?id=178

Comment #2 by jfitzell:
Name: Seaside-Core-jf.272
Author: jf
Time: 5 October 2008, 11:10:07 pm
UUID: 1b0da229-2569-ea4a-a0a9-f4795e6165d7
Ancestors: Seaside-Core-jf.271

Name: Seaside-Session-jf.24
Author: jf
Time: 5 October 2008, 11:10:46 pm
UUID: a2309386-49a7-dc4f-9eba-6970d060215d
Ancestors: Seaside-Session-jf.23

Name: Seaside-Tests-All-jf.24
Author: jf
Time: 5 October 2008, 11:11:20 pm
UUID: bd990a59-4469-b341-ab81-5dc6ecf963c9
Ancestors: Seaside-Tests-All-jf.23

Implement proper copying behaviour for WACache, its plugins, and WASession  
and
WARegistry which currently hold instances of WACache.

http://code.google.com/p/seaside/issues/detail?id=178

+ add private (for now) accessors for all the plugins on WACache (needed  
for testing,
but also good practice)
+ remove need for cache to be specified when initializing a cache plugin.  
It must
however be set with #setCache: before being used. This allows passing in a  
configured
plugin instance to WACache instead of a class and also makes it possible to  
change
the cache instance variable after copying.
+ Add test for WACache>>testCopy to test copy behaviour


Issue attribute updates:
	Status: Fixed

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