Thanks Paul, I am using new sessions and the problem seems to be okay locally, but not on the server. So I noticed that on the server (through the access portal we use) it forces a new session per tab. So the original issue with the modal window I thought I have found the session issue to be the culprit, but now even running locally I am getting page expirations when running locally. This happens on a page that I redirect to using a setResponsePage, and while this is up, and I open a new application instance inside of a new browser tab, the original tab's page expires right away. What should I be looking at to make sure this doesn't happen. I have been searching all over and I can't seem to find any real solutions to this issue.
-- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Error-in-Modal-opening-two-diffrent-instances-of-Wicket-applicaiton-tp4664418p4664521.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
