Invalidating a session in jsp

14-Dec-2015 07:42

Not logging off the user when they're done using the Web App rendering the Web I isn't the end of the world, but it would be very nice to do (reset state, free up resources on BO server, free up in-use licenses, allow BO user preferences e.g.

locale to take effect without waiting for a session timeout).====Incidentally, as a bit of a surprise to me, the following code and redirecting the user to the Open Document URL with a logon Token establishes two separate sessions.

There is a Session Map class which asks for a httpservletrequest as a parameter, and has an invalidate method for the http session, not sure how this works.

thanks in advance for your assistance as the last instruction of my page.

-- Alvaro Sanchez-Mariscal Arnaiz Java EE Architect & Instructor [hidden email] --------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] I agree too that (generally speaking) we must introduce the least possible quantity of scripting into JSP pages as we can, so we honor the MVC architecture, however, in this particular case (invalidating the session), I don't understand why would be better to do it in the action class rather than in the JSP page for non-small apps.2007/9/12, Alvaro Sanchez-Mariscal The only thing "wrong" with it is that now you are putting application control logic in a jsp page, which is 'OK' for small apps, and is probably 'OK' in this particular instance if there are no complicating factors.action class rather than in the JSP page for non-small apps. If you keep all of your code in the files, except for one or two lines that are in scriplets, it becomes a nightmare for anyone else to maintain the code.Calling logoff() on the bo Session below will close out the first session, but doesn't effect the Open Document session at all.Hey, How to invalidate a Http Sesssion in struts 2.0?

-- Alvaro Sanchez-Mariscal Arnaiz Java EE Architect & Instructor [hidden email] --------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] I agree too that (generally speaking) we must introduce the least possible quantity of scripting into JSP pages as we can, so we honor the MVC architecture, however, in this particular case (invalidating the session), I don't understand why would be better to do it in the action class rather than in the JSP page for non-small apps.2007/9/12, Alvaro Sanchez-Mariscal The only thing "wrong" with it is that now you are putting application control logic in a jsp page, which is 'OK' for small apps, and is probably 'OK' in this particular instance if there are no complicating factors.action class rather than in the JSP page for non-small apps. If you keep all of your code in the files, except for one or two lines that are in scriplets, it becomes a nightmare for anyone else to maintain the code.Calling logoff() on the bo Session below will close out the first session, but doesn't effect the Open Document session at all.Hey, How to invalidate a Http Sesssion in struts 2.0?We're running into a problem with the use of Open Document.