The servlet container uses this interface to create a session between an HTTP client and an HTTP server. The session persists for a specified time period, across more than one connection or page request from the user. A session usually corresponds to one user, who may visit a site many times. The server can maintain a session in many ways such as using cookies or rewriting URLs.
This interface allows servlets to
When an application stores an object in or removes an object from a session, the session checks whether the object implements HttpSessionBindingListener . If it does, the servlet notifies the object that it has been bound to or unbound from the session. Notifications are sent after the binding methods complete. For session that are invalidated or expire, notifications are sent after the session has been invalidated or expired.
When container migrates a session between VMs in a distributed container setting, all session attributes implementing the HttpSessionActivationListener interface are notified.
A servlet should be able to handle cases in which
the client does not choose to join a session, such as when cookies are
intentionally turned off. Until the client joins the session,
true. If the client chooses
not to join
getSession will return a different session
on each request, and
isNew will always return
Session information is scoped only to the current web application
ServletContext), so information stored in one context
will not be directly visible in another.
|Method from javax.servlet.http.HttpSession Summary:|
|getAttribute, getAttributeNames, getCreationTime, getId, getLastAccessedTime, getMaxInactiveInterval, getServletContext, getSessionContext, getValue, getValueNames, invalidate, isNew, putValue, removeAttribute, removeValue, setAttribute, setMaxInactiveInterval|
|Method from javax.servlet.http.HttpSession Detail:|
public Object getAttribute(String name)
public Enumeration getAttributeNames()
public long getCreationTime()
public long getLastAccessedTime()
Actions that your application takes, such as getting or setting a value associated with the session, do not affect the access time.
public int getMaxInactiveInterval()
public HttpSessionContext getSessionContext()Deprecated!
public Object getValue(String name)Deprecated!
public String getValueNames()Deprecated!
public void invalidate()
public boolean isNew()
public void putValue(String name, Object value)Deprecated!
public void removeAttribute(String name)
After this method executes, and if the object
public void removeValue(String name)Deprecated!
public void setAttribute(String name, Object value)
After this method executes, and if the new object
If an object was already bound to this session of this name
If the value passed in is null, this has the same effect as calling
public void setMaxInactiveInterval(int interval)