Yes we have been experienced those... Are you using tapestry 3 or tapestry 4? Which servlet engine? Since we switched to tapestry 4, we have seen way less of these... And I'm 99% positive this has not anything to do with the code.
On 6/5/06, John Menke <[EMAIL PROTECTED]> wrote:
Is anyone experiencing any problems with "lost" session variables? We have an application that stores some state in the session and we are getting strange errors caused by objects that were previously being in the session being "lost". When our code tries to access these variables it gives nullpointer errors. What is strange is that the session is not being lost itself - if this was the case the StaleSession page would appear via tapestry... -jm
-- Thanks, Henri.
