I read the Java Serialization spec and don't understand the line about the no-arg constructor.
Since different tiers (web vs bisiness) as well as HttpSession migration often uses serialization to pass objects through the "wire", it seems important. Here is the line from the spec: A Serializable class must do the following: ..... Have access to the no-arg constructor of its first non-serializable superclass .... What does this mean and why do you need this requirement? But it does seem to say that you do NOT need your class declared with "implements Serializable" to have a no-arg constructor, correct? Thanks, Yaakov. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
