The problem here is the session somehow being accessed after invalidate() is called. Maybe you tried to set an @Persist'd variable or something, and the actual change didn't propagate until after you called invalidate().
I do my invalidate in an ajax request. The other solution is to call invalidate in a filter, so it always ends up after any session altering code. -- View this message in context: http://tapestry-users.832.n2.nabble.com/Error-after-logout-tp6036478p6036628.html Sent from the Tapestry Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
