On Mon, Apr 6, 2009 at 9:29 AM, Volker Lamp <volker.l...@gmail.com> wrote:
> While attempting to upgrade my webapp to Tapestry 5.1.0.2 from Tapestry > 5.0.18 I run into a problem related with tapestry-spring-security 2.0.1. > Triggering LogoutService.logout() in a 5.1.0.2 environment results in a > IllegalStateException which was not the case in 5.0.18. > From a recent discussion in another thread in this list [1] as well as the > comments in TAP5-413 I suppose the problem's root is that Spring Security's > SecurityContextLogoutHandler.logout() [3] actually invalidates the Servlet > API HttpSession rather than Tapestry's Session. I'm having this issue too. Besides this, the @Secured annotation does not work. -- Thiago --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
