On Sun, May 23, 2004 at 02:25:27PM -0500, Barnet Wagman wrote:
: Does Tomcat, by default, serialize a session (or anything else)?
1/ Tomcat loads/stores sessions by default on container
startup/shutdown. See the last item on:
http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/manager.html
For the archives, the excerpt from that page is:
- - - begin - - -
Special Features
Restart Persistence
Whenver Catalina is shut down normally and restarted, or when an
application reload is triggered, the standard Manager implementation
will attempt to serialize all currently active sessions to a disk file
located via the pathname attribute. All such saved sessions will then be
deserialized and activated (assuming they have not expired in the mean
time) when the application reload is completed.
In order to successfully restore the state of session
attributes, all such attributes MUST implement the java.io.Serializable
interface. You MAY cause the Manager to enforce this restriction by
including the <distributable> element in your web application deployment
descriptor (/WEB-INF/web.xml).
- - - end - - -
2/ The spec (sort of) requires that session attrs be serializable: sec
7.7.2 for 2.3 and 2.4 requires it for distributed/clustered containers
(and leaves the handling of non-clustered configuration to container
implementors).
-QM
--
software -- http://www.brandxdev.net
tech news -- http://www.RoarNetworX.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
