I have this session attribute containing an Object.
I also have a session time out set to 30 minutes.
In the servlet code I wrote the code below.
I also forward this object into a JSP page and use it for another purpose. So if I refresh the page when the session is timeout, it will gives me an error too =(
The problem is, when the session is timeout and when I requested the servlet, it gives me an error stating that the object is null or empty.
Does any one knows how to mitigate this problem?
I heard that I must use a listener or a filter. But could anyone here please enlighten me how to solve this problem please.
Whenever you fetch a scoped variable from the session using getAttribute() you test it for null. When the session times out, all scoped variables palced in the session are dumped.
(One reason testing for session nullity isn't a great idea is that a JSP page will automagically create a session, unless you explicitly configure it not to. It's simply too easy to forget to do that, and not worth the effort. Checking for a session attribute is much simpler, and less error-prone.)
Ouchhhhhhhh Sir Sheriff Bear, it does not work hmmmmmm. But when I use the previous way "Checking the session null", it does forward the request to another JSP page.
I got this kind of error when I call the servlet again
So it is best practice or better to check the session attribute nullity rather than checking the session object nullity.
so if the session attribute is destroyed/expired/timeout, I must create a new session attribute filled with an object and a value such as a boolean which tells the visitor is not a member. Then in a JSP page it will use that boolean information to hide the special feature and display the login/signup button.
hehehehehe sorry I made too much statement instead of an question.