Alright, switched to elephant-1.0 and bdb 4.7. Now I get a strange
error however - supposedly elephant:owned-txn-p is deprecated. Is
weblocks using that function somewhere?:
-------------------------------------------------------------------------------------------------------------------------------
Function is deprecated
[Condition of type SIMPLE-ERROR]
Restarts:
0: [TERMINATE-THREAD] Terminate this thread (#<THREAD "Processing
action" RUNNING {100583AAC1}>)
Backtrace:
0: ((LAMBDA (SWANK-BACKEND::DEBUGGER-LOOP-FN)) #<FUNCTION (LAMBDA #)
{1008879049}>)
1: (SWANK::DEBUG-IN-EMACS #<SIMPLE-ERROR {1004510AC1}>)
2: (SWANK-BACKEND::CALL-WITH-BREAK-HOOK #<FUNCTION SWANK:SWANK-
DEBUGGER-HOOK> #<CLOSURE (LAMBDA #) {1004510F79}>)
3: ((LAMBDA (SWANK-BACKEND::HOOK SWANK-BACKEND::FUN)) #<FUNCTION
SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA #) {1004510F79}>)
4: (SWANK::CALL-WITH-BINDINGS ..)
5: (SWANK::CALL-WITH-CONNECTION #<SWANK::CONNECTION {1003B63931}>
#<CLOSURE (LAMBDA #) {1004510F79}>)
6: (SWANK:INVOKE-SLIME-DEBUGGER #<SIMPLE-ERROR {1004510AC1}>)
7: (SWANK-BACKEND::CALL-WITH-BREAK-HOOK #<FUNCTION SWANK:SWANK-
DEBUGGER-HOOK> #<CLOSURE (LAMBDA #) {1004510F39}>)
8: ((LAMBDA (SWANK-BACKEND::HOOK SWANK-BACKEND::FUN)) #<FUNCTION
SWANK:SWANK-DEBUGGER-HOOK> #<CLOSURE (LAMBDA #) {1004510F39}>)
9: (SWANK:SWANK-DEBUGGER-HOOK #<SIMPLE-ERROR {1004510AC1}>
#<unavailable argument>)
10: (SB-DEBUG::RUN-HOOK *DEBUGGER-HOOK* #<SIMPLE-ERROR {1004510AC1}>)
11: (INVOKE-DEBUGGER #<SIMPLE-ERROR {1004510AC1}>)
12: ((FLET #:LAMBDA13) #<SIMPLE-ERROR {1004510AC1}>)
13: (SIGNAL #<SIMPLE-ERROR {1004510AC1}>)[:EXTERNAL]
14: (ERROR "Function is deprecated")[:EXTERNAL]
15: (ELEPHANT::OWNED-TXN-P #<unavailable argument> #<unavailable
argument>)
16: ((SB-PCL::FAST-METHOD WEBLOCKS:DYNAMIC-TRANSACTION (WEBLOCKS-
ELEPHANT:ELEPHANT-STORE T)) ..)
17: (WEBLOCKS::ACTION-TXN-HOOK (#<FUNCTION # {1008945A99}>))
18: ((LAMBDA ()))
19: ((SB-PCL::FAST-METHOD WEBLOCKS:HANDLE-CLIENT-REQUEST
(WEBLOCKS:WEBLOCKS-WEBAPP)) #<unavailable argument> #<unavailable
argument> #<unavailable argument>)
--more--
-------------------------------------------------------------------------------------------------------------------------------
On Feb 9, 11:42 pm, "Leslie P. Polzer" <[email protected]>
wrote:
> MHOOO wrote:
> > For some reason I get a controller-lost-error from elephant whenever
> > weblocks tries to set the value of one of my persistent classes. It
> > works however if I do it manually from elephant.
> > My Store Definition (elephant clsql test-suite ran without problems):
>
> Elephant-CLSQL is no longer supported. Weblocks-Elephant probably uses
> parts that are broken in Elephant-CLSQL. Use Elephant-BDB or
> Elephant-Postmodern instead.
--
You received this message because you are subscribed to the Google Groups
"weblocks" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/weblocks?hl=en.
