Invalidating a session in java
Illegal State Exception: get Last Accessed Time: Session already invalidated at org.apache.catalina.session.Standard Last Accessed Time(Standard Session.java:423) at org.apache.catalina.session.I keep on saying that you can perform exactly the same with Logout Action, but keeping away code from JSP.
The point about keeping code in the code and presentation in the presentation is the only argument necessary: when I look for functionality I look in the code, not the JSP.Blocking Response State.block(Blocking Response State.java:117) at com.icesoft.faces.webapp.xmlhttp.Blocking Servlet.execute Request(Blocking Servlet.java:288) at com.icesoft.faces.webapp.xmlhttp. Blocking Servlet.service(Blocking Servlet.java:189) at javax. Http Servlet.service(Http Servlet.java:802) at org.apache. Application Filter Chain.internal Do Filter(Application Filter Chain.java:252) at org.apache.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.They would never think to look in the files for Java code, because that's not where the logic lives and it slows down the whole process of maintaining the site, or bringing people up to speed to maintain the site, so you can go off and do the fun things.
Nobody gave any examples, counter-examples or use cases that shows it is more convenient to do it in the action.