So the session sees you as a different web app then the old application
Then you will get a new session.
Are you sure that the complete app (old and new) are running in the same web app under the same context?
johan
On 4/14/06, nils steen <[EMAIL PROTECTED]> wrote:
Hi,
I am on a project where the goal is to write a second front-end to an existing application. The existing application uses the HttpSession attributes to store the user's settings (language, encoding, authentication, permissions...)
I tried passing the httpSession to the existing application using:
ServletWebRequest req = (ServletWebRequest)this.getRequest(); //"this" is a WebPage
HttpSession httpSession = req.getHttpServletRequest().getSession();
However, the session passed to the backend isn't always the same one, causing the back-end to throw exceptions. Is there something i can do to maintain the httpSession (and keep it alive). How come i can't get the httpSession from the wicket session (like i can with the request)?
Understandably, modifying the existing application opens a whole new can of beans... and is outside the scope of the project.
Thanks for your help,
Nils
