hi, everyone: I have a question: how to handle the attributes stored in the session when this session is migrated from one JVM to another? I know the a new session is going to be created since session belong to the context. But how about the attributes in the session? They are re-enter into the new session automatically? Thanks in advance! Xiaoma Waang
First of all, the session data values must be of types that implement java.lang.Serializable, so that the distributed JVM can accept the HttpSession object. (please ref. Servlet spec.) But I think the most safe way to storge application data is to storge them into EJB or Database.
Sun Certified Web Component Developer for the J2EE Platform<br />Sun Certified Programmer for the Java 2 Platform<br />Oracle Certified Associate
posted 17 years ago
hi, Janson: You suggestion is right. Save in the ejb or database is a good idea, if multiple JVMs are involved in the web design. Thank you very much! Xiaoma Wang
I'm doing laundry! Look how clean this tiny ad is:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop