have you tried with a different servlet container for instance tomcat? i've experienced the same session problems with a custom webapp deployed on jetty some time ago. the sessionid was used to track the session and we had the same problem as you describe in a single instance of jetty. -- View this message in context: http://www.nabble.com/Invoulentary-session-sharing-leakage-in-Wicket-1.3.x-tp16550360p16585502.html Sent from the Wicket - User mailing list archive at Nabble.com.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
