Yep, it does not solve my problem. Being on another page than the one setting the object in session, discarding will not remove my object of interest. Still digging for a solution. I wonder if I could just cast the session back to a Servlet HttpSession and just invoke removeAttribute from there. That will be leaving Tap scope a bit, so i'm reluctant to do it that way.
-- View this message in context: http://tapestry.1045711.n5.nabble.com/removing-attributes-from-session-from-pages-other-than-the-one-setting-it-tp4592795p4592891.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
