The reason why signin2 fails because first the session gets invalidated (by SignOut.onEndRequest() and that Wickets cluster management (request lifecycle mgmt) detects a dirty session and tries to update an attribute (session.setAttribute). Because the session is invalide, that causes an exception. Now I have a question, though it is probably simple to detect that the session is invalid and not do any modifications to it, what happens to the session on the remaining members of the clusters? Does the container automatically detect invalid sessions and invalids them on the remaining members as well?
Juergen ------------------------------------------------------- This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005 Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows Embedded(r) & Windows Mobile(tm) platforms, applications & content. Register by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
