From: wolfmanstout <wol...@ya...> - 2007-08-21 23:36:59
|
For a while now, I've been having a bug where sometimes my eXist page would= give me an error saying "getAttribute: Session already invalidated." This= would always happen if I had not accessed the page for a while (implying t= hat it the session had expired). Nevertheless, the very first thing I did = in my XQuery script was session:create(), and nowhere was I invalidating it= , so the session should have been recreated. Before I continue any further= , know that I am running eXist-1.1.1-newcore.war inside Tomcat, and this sc= ript is being called by Cocoon. =0A=0AAfter much unsuccessful tweaking of = various details of the script, I finally realized that the error could be r= eproduced with an extremely simple script:=0A=0Axquery version "1.0";=0Adec= lare namespace session=3D"http://exist-db.org/xquery/session";=0Asession:cr= eate(), session:invalidate()=0A=0AAll I have to do is access this two times= in succession, and from the second run onward the script will continually = produce that error message. I wondered whether this had to do with lazy ev= aluation, so I made the invalidate() call dependent on create() running fir= st:=0A=0Aif (not(session:create())) then session:invalidate() else ()=0A=0A= This didn't solve the problem. Unless I'm misunderstanding what these func= tions should be doing, it seems to me that both of these scripts should wor= k. Session:create() creates a session if none exists, so it shouldn't matt= er whether a previous session has been invalidated or not. =0A=0AAny ideas= ?=0A=0AThanks a bunch,=0A~James=0A=0A=0A=0A=0A =0A___________________= _________________________________________________________________=0ASick se= nse of humor? Visit Yahoo! TV's =0AComedy with an Edge to see what's on, wh= en. =0Ahttp://tv.yahoo.com/collections/222 |