I am running into a problem trying to determine when a conversation starts and more specifically ends with Tapestry. I understand that Tapestry issues some redirects or creates a new request(s) for the render cycle. Is there a way to determine when a conversation is completed and the page has been rendered?
Right now, I have a Servlet Filter that puts an attribute into the HttpSession. I want to clean that attribute up when the conversation is over and tapestry is done with all of its requests/redirects/rendering. I have looked at contributing a requestHandler but it seems to be called on both the action and render requests. I looked at contributing a Master Dispatcher, but I don't think that is what I want to do, so I didn't pursue it too far. Any ideas? -- View this message in context: http://www.nabble.com/-T5--Request-Management-tp21253367p21253367.html Sent from the Tapestry - User 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
