[Seaside-dev] filters initialization with request context?

[Lukas Renggli]

> the database pool receives aBlock and it will evaluate the things of the app in
> the continuation.
> So in the pool I make something like:
>
>        [aBlock evaluateIn: aTransaction] ensure:[ aTransaction commit]
>
> and aTransaction goes and try to commit but all its instVars are in nil.
> Is this a continuation effect of not copying those after evaluating aBlock? how
> would you do something like this?

That look weird. It could well be an effect of full continuations, but
then again I don't see how aTransaction ends up in the stack. Do you
register that object for backtracking?

Could you try to update to the latest code to see if the problem
persists? Evaluate "WADevelopment updateWorkingCopies" until it
doesn't throw errors anymore. Evaluate it again, and close with
"WADevelopment recompile" and "WAAdmin initialize".

Cheers,
Lukas

-- 
Lukas Renggli
http://www.lukas-renggli.ch