Re: Issue 147 in glassdb: Seaside3.0 errors occuring above Session don't get continuations stashed .. they should

Issue 147: Seaside3.0 errors occuring above Session don't get continuations  
stashed .. they should
http://code.google.com/p/glassdb/issues/detail?id=147

This issue is now blocking issue 191.
See http://code.google.com/p/glassdb/issues/detail?id=191

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

Updates:
        Labels: -Milestone-3.0 Milestone-1.0-beta.8.5

Comment #4 on issue 147 by [hidden email]: Seaside3.0 errors occuring  
above Session don't get continuations stashed .. they should
http://code.google.com/p/glassdb/issues/detail?id=147

now's a good time to get this one done

Updates:
        Labels: -Milestone-1.0-beta.8.5 Milestone-1.0-beta.9

Comment #5 on issue 147 by [hidden email]: Seaside3.0 errors occuring  
above Session don't get continuations stashed .. they should
http://code.google.com/p/glassdb/issues/detail?id=147

all of the error handler on the stack about the WAExceptionHanlder for  
Seaside log entries in the object log, but to-date no commit is being  
done ... it is just possible that a commit at the very bottom of the stack  
could be done (unconditionally) which would cause any object log entries to  
be committed ...

To do this I'll need to do a lot of testing/code review to flush out any  
possible problems with this approach ... defer to a later release...

Updates:
        Labels: -Milestone-1.0-beta.9 Milestone-3.0

Comment #6 on issue 147 by [hidden email]: Seaside3.0 errors occuring  
above Session don't get continuations stashed .. they should
http://code.google.com/p/glassdb/issues/detail?id=147

(No comment was entered for this change.)