[Seaside-dev] Issue 175 in seaside: WAExpiryFunctionalTest broken

[codesite-noreply at google.com]

Issue 175: WAExpiryFunctionalTest broken
http://code.google.com/p/seaside/issues/detail?id=175

Comment #2 by jfitzell:
Well, it's mostly fixed. I removed the edit box for the expiry time, since  
that
currently has no effect. Instead of "expiry" we now simply unregister the  
session and
then redirect. You would think unregistering the session would be enough  
but if you
don't immediately redirect, something ends up automatically re-registering  
the
session under a new key. This is kind of lame.


Name: Seaside-Development-jf.8
Author: jf
Time: 7 October 2008, 6:54:24 pm
UUID: 762ca865-2216-2c48-bae8-6147a3eb835f
Ancestors: Seaside-Development-jf.7

Name: Seaside-Session-jf.27
Author: jf
Time: 7 October 2008, 6:52:39 pm
UUID: 7d365dbe-da08-e941-8561-f41d5dbdcef9
Ancestors: Seaside-Session-jf.26

Name: Seaside-Core-jf.277
Author: jf
Time: 7 October 2008, 6:51:01 pm
UUID: d63faead-0370-b143-9852-dac590725059
Ancestors: Seaside-Core-jf.276

Name: Seaside-Tests-Functional-jf.4
Author: jf
Time: 7 October 2008, 6:56:58 pm
UUID: cd94de55-96f6-4b4c-b108-461e876600ca
Ancestors: Seaside-Tests-Functional-obi.3

Name: Seaside-Tests-Core-jf.10
Author: jf
Time: 7 October 2008, 6:57:37 pm
UUID: 31092883-9855-ac41-8813-2cc512354be8
Ancestors: Seaside-Tests-Core-jf.9


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