I was under the impression that when I call Session.replaceSession() a new session would be created.
I am seeing a new HttpServletSession being created but not my wicket application session. I have placed a System.out.println( "new AppSession()..." ) in the constructor and I am not seeing that. Can anyone confirm this behavior as well? Is this a bug? Is there a work around? I am using Wicket 1.4.9 BTW...my use case is someone goes to the LoginPage and logs in, the previous session will be cleared. Multi-window support is also on (however...changing this doesn't affect the outcome) Thanks - Doug
