Re: [Tapestry-developer] Stale session

[Dave Roberts]

Sorry to bug you guys about this one, but it has been a couple of days and I still haven't figured it out. Maybe I'm dense, but I can't seem how to get this working. Given that Christian Sell just ran into what sounds like the same thing, either something is broken in Tapestry 2.2, it's something environment specific, or something is not obvious to Tapestry newbies like us. To provide a bit more background:   I'm using Tapestry 2.2 with Eclipse, Spindle 1.1.3, the Jetty version packaged with Tapestry 2.2. I have written a quick little Main class that sets up Jetty and gets things going. I have Tapestry working enough to create a few pages, use PageLinks, a Form, etc. It's just DirectLink that I have problems with right now.   Can somebody explain how, exactly, Tapestry as a framework decides the session is stale? I even looked at the source in the DirectService class and didn't see anything there that looked like it even checked or threw an exception related to a stale session.   Thanks,   -- Dave Roberts [EMAIL PROTECTED] ----- Original Message ----- From: Dave Roberts To: [EMAIL PROTECTED] Sent: Thursday, December 12, 2002 8:52 PM Subject: [Tapestry-developer] Stale session I'm trying to do my first bit of real programming using Tapestry. I have successfully made a page that implements a form and allows me to add records to a database via JDBC. I'm now working on a page that displays all the records and includes a "Delete" DirectLink to delete a record, using the record ID as the DirectLink parameter. I can't seem to get it to work. The form displays all the records correctly using a Foreach, but every time I click on the Delete links, I get a Stale Session page.   I have tried to work around this using the "stateful" parameter binding and setting this to "false," but it doesn't seem to have any effect.   Any suggestions for how to debug this? I haven't had to deal with Visit objects yet and haven't explicitly created any during my processing. I tried adding a "net.sf.tapestry.visit-class" parameter to the application, pointing this to java.lang.Object for now since I don't have any data to actually store. I still get the same behavior.   Thanks for any suggestions.   -- Dave Roberts [EMAIL PROTECTED]