在一个软件项目中,在很多情况下,都需要传输数据,可以使用Java IO包中的ObjectOutputStream和ObjectInputStream来处理。通常,数据以二进制格式写入,因此我们无法查看内容。序列化是将对象写入输出流的过程。我们可以编写一个类对象本身,它包含原始数据类型和Java对象图的组合。反序列化是从输入流重建对象的过程。
实现:让我们看看 ObjectOutputStream 我们为它创建了一个名为“VehicleSpecifications”的 POJO 类。
Note: It should implement Serializable, otherwise, java.io.NotSerializableException will be thrown.
示例 1:
Java
Java
Java
No output is as till now by far we have implemented just the constructors and defined body of methods including getters and setters.
Now let us create a few vehicle specifications and write them in a file. As VehicleSpecifications implemented Serializable functionality, the data can be written to a file in a binary format. For this we will be using “writeObject” function and by using that we can write class attributes using write methods provided by ObjectOutputStream.
示例 2:
Java
注意:在执行上面的代码时,我们可以看到数据是以二进制格式写入的,这意味着它只是一种不可读的格式。
所以为了以可读的格式获取数据,我们使用ObjectInputStream,因为我们必须检索类对象数据(即VehicleSpecifications数据),我们需要使用readObject ()方法,该方法可以使用read()读取类属性ObjectInputStream提供的方法。
示例 3:
Java
输出:
输出说明:
因此,我们看到的是人类可读格式的输出。因此,我们的整个类对象集可以使用Java.io 包提供的 ObjectInput 和 ObjectOutput 流进行移植。因此,现在让我们在对 ObjectOutputStream 和 ObjectInputStream 的内部工作流程有一个了解之后,最终讨论它们之间的区别。它们以表格格式显示如下:
ObjectOutputStream | ObjectInputStream |
---|---|
Writes Java objects | Reads Java objects |
Using ArrayList, we can write multiple Java objects | Via ArrayList, we can read and retrieve multiple Java objects |
By default, ArrayList is serializable, and hence no need to implement serializable if we are writing ArrayList of objects like String, but the elements should be serializable. writeObject() is used to write ArrayList of data | During deserialization of ArrayList object, readObject() is used to read the ArrayList of data |
If we are using a class object(like the example as we discussed above), the class should implement serializable and then only while using writeObject() method, java.io.NotSerializableException will not be thrown | We need to cast the same format of object while using readObject() |
writeObject() method writes the serialized data in binary format | readObject() method deserializes and reads the data |
The binary format is not readable. Though we are passing primitive data like String, double, etc., while writing, the data is getting stored in binary format. | In order to get the data in perfect class format, we need to use ObjectInputStream which deserializes data and we can get all primitive data that is written |
As a whole object, it is getting written, there is no loss of data provided the object is serialized and written in a proper format | Similarly, whole object is read, there is no loss of data, and we can easily iterate the data also. |
Not only writing class objects by means writeObject(), it also supports other write methods like as depicted below and many more methods to write for each and every data type. write(byte[] buffer)-> Writes an array of bytes. writeBoolean(boolean value) -> Write boolean value writeDouble(double value)-> Write 64 bit double value writeInt(int value)-> Writes 32 bit int |
Not only reading class objects by means readObject(), it also supports other read methods like depicted as below and many more methods to read each and every datatype. read()-> Reads byte of data readBoolean() -> To read a boolean. readDouble()-> To read a 64 bit double. readInt()->To Read a 32 bit int. |
Possible exceptions for ObjectOutputStream is as follows: IOException – in case of any I/O error occurs during writing stream header SecurityException NullPointerException – if OutputStream not initialized and hence it may be null |
Possible exceptions for ObjectInputStream is as follows: StreamCorruptedException – Incorrect stream header IOException – In case of any I/O error occurs while reading stream header SecurityException NullPointerException – if Inputstream not initialized and hence it may be null |
Possible exceptions for writeObject is as follows: InvalidClassException – Serialization of class should be correct and if something is wrong. NotSerializableException – Some object to be serialized does not implement the java.io.Serializable interface. This will commonly occur and hence it is mandatory to make the class to implement Serializable IOException – During writing, if IO error occur by the underlying OutputStream. |
Possible exceptions for readObject is as follows: InvalidClassException – Serialization of class should be correct and if something is wrong. ClassNotFoundException – Class of a serialized object should be available and if cannot be found. IOException – During reading, if IO error occur by the underlying InputStream StreamCorruptedException OptionalDataException |