When I try it out on my computer - restart the tomcat service and then access the various attributes - the session attribute value is still available (though the application attributes have been lost ofcourse).
So is this container dependent or will the session object always exist, till it times out or is invalidated?
"A problem well stated is a problem half solved.” - Charles F. Kettering
SCJP 6, OCPJWCD
Creator of Enthuware JWS+ V6