Java Serialization | Java Externalization |
Process of writing the state of an object to byte stream | Externalization is a customized serialization process that give the class complete control over the format and contents of the stream for an object and its super types. Allows to modify the stream before being serialized. For example the stream can be compressed from BMP to JPEG or can be encoded/decoded. |
Achived by impementing the java.io.Serializable interface | Achived by impementing the java.io.Externalizable interface |
Marker interface with no methods | Not Marker interface. Has readExternal(ObjectInput in) and writeExternal(ObjectOutput out) methods |
Serialization is the process of converting an object into a sequence of bits so that it can be persisted on a storage medium (such as a file, or a memory buffer) or transmitted across a network connection link. This process of serializing an object is also called deflating or marshalling an object.
The serialization mechanism has been added into the Java language for two reasons:
(1) the JavaBeans mechanism uses serialization.
(2) remote method invocation (RMI) allows you to automatically use objects located at another host in the network just like any local objects.
In order to serialize an object, you need the output stream OutputStream, which must be put into the special serialization stream called ObjectOutputStream. After that, you only need to call the method writeObject() to serialize the object and send it to the output stream. . Classes ObjectInputStream and ObjectOutputStream, which respectively implement the ObjectInput and ObjectOutput interfaces, enable entire objects to be read from or written to a stream (possibly a file). To use serialization with files, we initialize ObjectInputStream and ObjectOutputStream objects with stream objects that read from and write to files—objects of classes FileInputStream and FileOutputStream, respectively
Vinayworld class implements serializable interface.
1.
Import java.io.serializable;
2.
Class vinayworld
implements
Serializable {
3.
Public String vinay_variable;
4.
Private String vinay_add;
5.
}
Other class would be
01.
Public
class
vinayotherClass {
02.
Public
static
void
main (String args[])
03.
{
04.
FileOutputStream fos=
new
FileOutputStream(
"vinay.txt"
);
05.
ObjectOutputStream oos=
new
ObjectOutputStream(fos);
06.
Vinayworld vw =
new
vinayworld();
07.
oos.writeobject(vw);
08.
oos.flush();
09.
oos.close();
In this code object of the vinayworld class is serialized into a file name vinay.txt
Serialization is a Marker interface -Marker Interface is used by java runtime engine (JVM) to identify the class for special processing.
Use serialization when you need to add data to the serialization stream that is not an object data member.
Externalization is same as Sterilization except that WriteObject() and ReadObject() method are called by JVM during sterilization an desterilization of object. One thing you can do with Externalization is that you can store extra information into object like STATIC variables and transient variables or you can add more information if you have any business need. One good example is compressing and uncompressing of data to send it through network or converting one format to other like a BMP image to JPEG or GIF format.
Externalization allows you to customize how serialization is done. By implementing externalization you are controlling what gets serialized ( and what doesnot ) as versus default serialization where all non-transient attributes get serialized.
For “fat data” classes with a large number of attributes only a few of which needs to persisted, externalization will help you reduce the size of serialized stream and the time taken to serialize the object. But there will be an overhead involved because the runtime has to call your methods to read/write objects.
Performance issue –
1. Further more if you are subclassing your externalizable class you will want to invoke your superclass’s implementation. So this causes overhead while you subclass your externalizable class.
2. methods in externalizable interface are public. So any malicious program can invoke which results into lossing the prior serialized state.
Difference between serialization and externalization: When you serialize an Externalizable object, a default constructor will be called automatically; only after that will the readExternal() method be called.Use the Externalizable interface when you need complete control over your bean’s serialization (for example, when writing and reading a specific file format).
No comments:
Post a Comment