> From: "J. Ryan Earl" <[EMAIL PROTECTED]> > Sent: Friday, April 22, 2005 7:44 AM
> How does Tomcat know what to serialize? Does it just use the Reflection > package and serialize out -everything- that implements java.io.Serializable? When you do a "setAttribute(key, object)", it serializes the object out for replication, so, both your key and object needs to be serializable. It uses the generic Java writeObject method. This is why you need to use setAttribute to ensure your changes are replicated, and why you can not just change an object directly and expect it to be replicated. So, if you are storing, say, a long ArrayList of objects in your session (like, say, query results), you must use setAttribute(yourList) each time you make a change to anything in the list, and then it serializes the ENTIRE list for replication, not just your changes. (And thus we see some of the limits of replication, at least some of the things you need to be aware of.) Regards, Will Hartung ([EMAIL PROTECTED]) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
