<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Java Serializable and serialVersionUID</title>
	<atom:link href="http://www.nilspreusker.de/2010/01/14/java-serializable-and-serialversionuid/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nilspreusker.de/2010/01/14/java-serializable-and-serialversionuid/</link>
	<description>Pragmatic Technologist</description>
	<lastBuildDate>Wed, 05 May 2010 20:11:58 +0200</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Arnold Reuser</title>
		<link>http://www.nilspreusker.de/2010/01/14/java-serializable-and-serialversionuid/comment-page-1/#comment-519</link>
		<dc:creator>Arnold Reuser</dc:creator>
		<pubDate>Thu, 18 Feb 2010 15:53:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.nilspreusker.de/?p=317#comment-519</guid>
		<description>First of all thanks for writing such a clear post on this topic. 

Without diving too deep in the subject I would like to add that one could also use the 
Externalizable interface instead of Serializable. This interface extends 
the java.io.Serializable interface and adds two methods  :

public void writeExternal(ObjectOutput out) 
public void readExternal(ObjectInput in) 

These methods are automatically called during serialization and de-serialization. 
Therefore, by providing code for these methods, you can implement your own serialization-specific 
operations, and, thus, have control over what data to, or not to serialize.

As a result using the Externalizable interface will provide you fine grained control 
over the object which you would like to migrate to a newer version of a class.</description>
		<content:encoded><![CDATA[<p>First of all thanks for writing such a clear post on this topic. </p>
<p>Without diving too deep in the subject I would like to add that one could also use the<br />
Externalizable interface instead of Serializable. This interface extends<br />
the java.io.Serializable interface and adds two methods  :</p>
<p>public void writeExternal(ObjectOutput out)<br />
public void readExternal(ObjectInput in) </p>
<p>These methods are automatically called during serialization and de-serialization.<br />
Therefore, by providing code for these methods, you can implement your own serialization-specific<br />
operations, and, thus, have control over what data to, or not to serialize.</p>
<p>As a result using the Externalizable interface will provide you fine grained control<br />
over the object which you would like to migrate to a newer version of a class.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
