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 invalidatd or expired.
"The pathname specified may be relative, although it cannot extend outside the current servlet context. If the path begins with a "/" it is interpreted as relative to the current context root. ...."
"The pathname must begin with a "/" and is interpreted as relative to the current context root.............."
"One important aspect of the new servlet specification involves he ability of an included or forwarded servlet to access request information through attributes. The name of the attribute dependes on whether
RequestDispatcher.include() or RequestDispatcher.forward() was invoked."
"The values corrrespond to the parameters of the original
request, without regard to further forwarding. For example, if a forwarded servlet invokes req.getServletPath() the result will be the same as if the java.servlet.include.servlet_path attribute had been acquired with
if we store any resource (here it's the .jar file) in the bin directory of Tomcat and we write