Ah yes, thanks. That seems the least likely to cause interactions. -----Original Message----- From: Yu, Ed [mailto:[EMAIL PROTECTED] Sent: January 11, 2006 12:09 PM To: 'Tapestry users' Subject: RE: Invalidating the session
I remembered seeing something on the web saying that you could forward to a jsp and invalidate the session there. Hope that helps. -----Original Message----- From: Michael Prescott [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 11, 2006 11:41 AM To: [email protected] Subject: RE: Invalidating the session I've answered my own question. In Tapestry 3.0.3, the AbstractEngine's restart() method eventually invokes HttpResponse.sendRedirect() which makes it illegal to do any further writes to the response. That makes it impossible to alter this behavior. I could override the restart() method in my own engine, but there doesn't seem to be any accessible way of making the engine stateless. (This is required if you invalidate the session since the setAttribute() on an invalidated session throws IllegalStateException.) I'm getting the impression that it's impossible to invalidate the session without going to the home page unless I patch Tapestry. Michael _____ From: Michael Prescott Sent: January 11, 2006 10:54 AM To: [email protected] Subject: Invalidating the session I need to invalidate the session, and as I understand the typical way to do this is by calling restart() on the engine. Unfortunately, this also issues a redirect to the app's home page. For the moment, I can't let this happen - I need to have it go to another page entirely. Is it legal to call restart() and then activate another page? Michael Michael Prescott direct: 416.646.7062 main: 416.646.7000 fax: 416.646.7050 Exchange Solutions Inc. 250 Yonge Street, 18th Floor Toronto, ON M5B 2L7 www.exchangesolutions.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
