1. Introduction
In this article, we'll first understand the transient keyword, and then we'll see its behavior through examples.
2. Usage of transient
Let's first understand the serialization before moving to transient as it is used in the context of serialization.
Serialization is the process of converting an object into a byte stream, and deserialization is the opposite of it.
When we mark any variable as transient, then that variable is not serialized. Therefore, the serialization process ignores the original value of the variables and saves default values for that data type.
The transient keyword is useful in a few scenarios:
- We can use it for derived fields
- It is useful for fields that do not represent the state of the object
- We use it for any non-serializable references
3. Example
To see it in action, let's first create a Book class whose object we would like to serialize:
public class Book implements Serializable {
private static final long serialVersionUID = -2936687026040726549L;
private String bookName;
private transient String description;
private transient int copies;
// getters and setters
}
Here, we have marked description and copies as transient fields.
After creating the class, we'll create an object of this class:
Book book = new Book();
book.setBookName("Java Reference");
book.setDescription("will not be saved");
book.setCopies(25);
Now, we'll serialize the object into a file:
public static void serialize(Book book) throws Exception {
FileOutputStream file = new FileOutputStream(fileName);
ObjectOutputStream out = new ObjectOutputStream(file);
out.writeObject(book);
out.close();
file.close();
}
Let's deserialize the object now from the file:
public static Book deserialize() throws Exception {
FileInputStream file = new FileInputStream(fileName);
ObjectInputStream in = new ObjectInputStream(file);
Book book = (Book) in.readObject();
in.close();
file.close();
return book;
}
Finally, we'll verify the values of the book object:
assertEquals("Java Reference", book.getBookName());
assertNull(book.getDescription());
assertEquals(0, book.getCopies());
Here we see that bookName has been properly persisted. On the other hand, the copies field has value 0 and the description is null – the default values for their respective data types – instead of the original values.
4. Behavior With final
Now, let's see a special case where we'll use transient with the final keyword. For that, first, we'll add a final transient element in our Book class and then create an empty Book object:
public class Book implements Serializable {
// existing fields
private final transient String bookCategory = "Fiction";
// getters and setters
}
Book book = new Book();
When we verify the values after the deserialization, we'll observe that transient was ignored for this field, and the original value was persisted:
assertEquals("Fiction", book.getBookCategory());
5. Conclusion
In this article, we saw the usage of the transient keyword and its behavior in serialization and deserialization. We've also seen its different behavior with the final keyword.
As always, all the code is available over on GitHub.
The post The transient Keyword in Java first appeared on Baeldung.