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'd be interested to learn if anyone else is facing the same problem and has solutions or ideas for it. Best wishes, Volker [1] Thread "[T5 5.0.18] java.lang.IllegalStateException: Cannot create a session after the response has been committed" [2] http://issues.apache.org/jira/browse/TAP5-413 [3] http://acegisecurity.svn.sourceforge.net/viewvc/acegisecurity/spring-security/tags/spring-security-parent-2.0.4/core/src/main/java/org/springframework/security/ui/logout/SecurityContextLogoutHandler.java?view=markup -- View this message in context: http://n2.nabble.com/Tapestry-5.1.0.2-and-tapestry-spring-security-2.0.1-tp2592789p2592789.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
