Niclas Hedhman wrote:
On Saturday 15 January 2005 05:56, Antonio Gallardo wrote:
now I am confused.
Sorry :o(
Need I revert the changes?
Look at your use-case; Will the serialized data be used by more than one versioned instance of Cocoon (for instance, RMI between two Cocoons), OR persisted to survive an upgrade of a Cocoon version?
If not, then I suggest that no need to bother with serialVersionUID nor readObject/writeObject (except for that fact that both makes serialization faster).
If so, you need to make an active effort to keep serialization compatibility, just like a public interface/class elsewhere.
Does this answer it?
Yes :-)
Sylvain
-- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
