Basically, the compatibility stuff in cvs now is a single executable class, that uses java serialization to save serialversionuid's to disk for contract classes so that we can verify future classes against the serialized versions. The default behaviour is to do nothing, so it shouldn't cause any problems for those who don't use it.
When to use it:
In a certain situation (e.g. a freeze period before a release), the system could be configured to "make" serial versions, and after that, configured to "check", so that all subsequent changes to classes would need to be compatible with the versions created at "make" time.
If your class is to be configured to use compatibility, then it needs to:
* Implement Externalizable
* Define a public, no-args constructor (needed for the serialization/de-serialization)
...if it doesn't, then you will get warnings when using the compatibility module.
Expect bugfixes, updates and changes throughout the week.
Happy backwards compatibility.
:) Thomas
------------------------------------------------------------------------ ---------------------
Thomas Roka-Aardal; +47 97566202; +47 22331515; fax +47 22336024
Biskop Gunnerusgt. 2; Boks 805 Sentrum, 0104 Oslo;
www.conduct.no; [EMAIL PROTECTED]
------------------------------------------------------------------------ ---------------------
http://thepope.blog-city.com
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
