I am right now working on an application which has some 20 JSPs and 5 servlets. It is an appln where user logs into the system in two different modes and perform the operations. The back End is Oracle.
My concern now is, is it necessary to maintain a session. Though it may sound absurd, i am quite new to developing applications and this is my first one.
If so, how to get the session persisting for the entire application?
2 - by saying "we maintain session" i mean, incase we want to do somthing on session creation or destruction, like maintain logs of session in some file or in DB. then we have to do it for ourselves by implementing HttpSessionListener. this class is not found in the previous release of servlet specification. so we used to use HttpSessionBindingListener for this kind of implementation.
HttpSessionListener since Servlets 2.3; HttpSessionBindingListener since Servlets 2.0. HttpSessionBindingListener notifies when attributes are bound or unbound to/from the session, rather than when the session itself is created/destroyed. I guess you could contrive this pre-2.3 to perform the same functionality as the newer HttpSessionListener.