[Seaside-dev] Issue 187 in seaside: default WAFileHandler not registered

[codesite-noreply at google.com]

Issue 187: default WAFileHandler not registered
http://code.google.com/p/seaside/issues/detail?id=187

Comment #5 by jfitzell:
Fixed. Though I actually think this whole "default file handler" thing,  
while
convenient, is a bit too "magical" at the moment. Because every file  
handler instance
displays every library in the system, you have no opportunity to set up  
different
handlers with different setting (security for example) in the same image.

I'm not sure what the solution is but I'll file another issue about it...


Name: Seaside-Core-jf.256
Author: jf
Time: 28 September 2008, 4:39:50 pm
UUID: c0336344-dbc9-b440-a162-ac3f5aa193d2
Ancestors: Seaside-Core-pmm.255

Fix for http://code.google.com/p/seaside/issues/detail?id=187

Set the "default" WAFileHandler when loading applications in the  
environment.


Name: Seaside-Environment-jf.17
Author: jf
Time: 28 September 2008, 4:40:12 pm
UUID: f0884422-ee1f-8946-8090-ec1e4f00874c
Ancestors: Seaside-Environment-jf.16


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