OSGi, Eclipse Equinox, ECF, Virgo, Gemini, Apache Felix, Karaf, Aires, Camel, Eclipse RCP

HBase, Hadoop, ZooKeeper, Cassandra

Flex4, AS3, Swiz framework, GraniteDS, BlazeDS etc.

There is nothing that software can't fix. Unfortunately, there is also nothing that software can't completely fuck up. That gap is called talent.

About Me


Deep Copy And Shallow Copy

Lets first separate it out and see what each one means.

What is Shallow Copy?

Shallow copy is a bit-wise copy of an object. A new object is created that has an exact copy of the values in the original object. If any of the fields of the object are references to other objects, just the reference addresses are copied i.e., only the memory address is copied.

Shallow Copy

In this figure, the MainObject1 have fields "field1" of int type, and "ContainObject1" of ContainObject type. When you do a shallow copy of MainObject1, MainObject2 is created with "field3" containing the copied value of "field1" and still pointing to ContainObject1 itself. Observe here and you will find that since field1 is of primitive type, the values of it are copied to field3 but ContainedObject1 is an object, so MainObject2 is still pointing to ContainObject1. So any changes made to ContainObject1 in MainObject1 will reflect in MainObject2.

Now if this is shallow copy, lets see what's deep copy?

What is Deep Copy?

A deep copy copies all fields, and makes copies of dynamically allocated memory pointed to by the fields. A deep copy occurs when an object is copied along with the objects to which it refers.

Deep Copy

In this figure, the MainObject1 have fields "field1" of int type, and "ContainObject1" of ContainObject type. When you do a deep copy of MainObject1, MainObject2 is created with "field3" containing the copied value of "field1" and "ContainObject2" containing the copied value of ContainObject1.So any changes made to ContainObject1 in MainObject1 will not reflect in MainObject2.

Well, here we are with what shallow copy and deep copy are and obviously the difference between them. Now lets see how to implement them in java.

How to implement shallow copy in java?

Here is an example of Shallow Copy implementation

 1 class Subject {
 3   private String name;
 5   public String getName() {
 6     return name;
 7   }
 9   public void setName(String s) {
10     name = s;
11   }
13   public Subject(String s) {
14     name = s;
15   }
16 }
18 class Student implements Cloneable {
19   //Contained object
20   private Subject subj;
22   private String name;
24   public Subject getSubj() {
25     return subj;
26   }
28   public String getName() {
29     return name;
30   }
32   public void setName(String s) {
33     name = s;
34   }
36   public Person(String s, String sub) {
37     name = s;
38     subj = new Subject(sub);
39   }
41   public Object clone() {
42     //shallow copy
43     try {
44       return super.clone();
45     } catch (CloneNotSupportedException e) {
46       return null;
47     }
48   }
49 }
51 public class CopyTest {
53   public static void main(String[] args) {
54     //Original Object
55     Student stud = new Student("John", "Algebra");
57     System.out.println("Original Object: " + stud.getName() + " - "
58         + stud.getSubject().getName());
60     //Clone Object
61     Student clonedStud = (Student) stud.clone();
63     System.out.println("Cloned Object: " + clonedStud.getName() + " - "
64         + clonedStud.getSubject().getName());
66     stud.setStudentName("Dan");
67     stud.getSubject().setSubjectName("Physics");
69     System.out.println("Original Object after it is updated: " 
70         + stud.getName() + " - " + stud.getStudent().getName());
72     System.out.println("Cloned Object after updating original object: "
73         + clonedStud.getName() + " - " + clonedStud.getSubject().getName());
75   }
76 }

Output is:
Original Object: John - Algebra
Cloned Object: John - Algebra
Original Object after it is updated: Dan - Physics
Cloned Object after updating original object: John - Physics

In this example, all I did is, implement the class that you want to copy with Clonable interface and override clone() method of Object class and call super.clone() in it. If you observe, the changes made to "name" field of original object (Student class) is not reflected in cloned object but the changes made to "name" field of contained object (Subject class) is reflected in cloned object. This is because the cloned object carries the memory address of the Subject object but not the actual values. Hence any updates on the Subject object in Original object will reflect in Cloned object.


How to implement deep copy in java?

Here is an example of Deep Copy implementation. This is the same example of Shallow Copy implementation and hence I didnt write the Subject and CopyTest classes as there is no change in them.

 1 class Student implements Cloneable {
 2   //Contained object
 3   private Subject subj;
 5   private String name;
 7   public Subject getSubj() {
 8     return subj;
 9   }
11   public String getName() {
12     return name;
13   }
15   public void setName(String s) {
16     name = s;
17   }
19   public Person(String s, String sub) {
20     name = s;
21     subj = new Subject(sub);
22   }
24   public Object clone() {
25     //deep copy
26     try {
27       //Deep copy
28       Student s = new Student(name, subj.getName());
29       return s;
30     } catch (CloneNotSupportedException e) {
31       return null;
32     }
33   }
34 }
 Output is:
 Original Object: John - Algebra
 Cloned Object: John - Algebra
 Original Object after it is updated: Dan - Physics
 Cloned Object after updating original object: Dan - Physics


Well, if you observe here in the "Student" class, you will see only the change in the "clone()" method. Since its a deep copy, you need to create an object of the cloned class. Well if you have have references in the Subject class, then you need to implement Cloneable interface in Subject class and override clone method in it and this goes on and on.

There is an alternative way for deep copy.

Yes, there is. You can do deep copy through serialization. What does serialization do? It writes out the whole object graph into a persistant store and read it back when needed, which means you will get a copy of the whole object graph whne you read it back. This is exactly what you want when you deep copy an object. Note, when you deep copy through serialization, you should make sure that all classes in the object's graph are serializable. Let me explain you this alternative way with an example.

 1 public class ColoredCircle implements Serializable
 2 {
 3     private int x;
 4     private int y;
 6     public ColoredCircle(int x, int y){
 7         this.x = x;
 8         this.y = y;
 9     }
11     public int getX(){
12         return x;
13     }
15     public void setX(int x){
16         this.x = x;
17     }
19     public int getY(){
20         return y;
21     }
23     public void setX(int x){
24         this.x = x;
25     }
26 }
28 public class DeepCopy
29 {
30     static public void main(String[] args)
31     {
32         ObjectOutputStream oos = null;
33         ObjectInputStream ois = null;
35         try
36         {
37             // create original serializable object
38             ColoredCircle c1 = new ColoredCircle(100,100);
39             // print it
40             System.out.println("Original = " + c1);
42             ColoredCircle c2 = null;
44             // deep copy
45             ByteArrayOutputStream bos = new ByteArrayOutputStream(); 
46             oos = new ObjectOutputStream(bos); 
47             // serialize and pass the object
48             oos.writeObject(c1);   
49             oos.flush();               
50             ByteArrayInputStream bin = 
51                     new ByteArrayInputStream(bos.toByteArray()); 
52             ois = new ObjectInputStream(bin);                  
53             // return the new object
54             c2 = ois.readObject(); 
56             // verify it is the same
57             System.out.println("Copied   = " + c2);
58             // change the original object's contents
59             c1.setX(200);
60             c1.setY(200);
61             // see what is in each one now
62             System.out.println("Original = " + c1);
63             System.out.println("Copied   = " + c2);
64         }
65         catch(Exception e)
66         {
67             System.out.println("Exception in main = " +  e);
68         }
69         finally
70         {        
71             oos.close();
72             ois.close();
73         }
74     }
75 }

 The output is:
 Original = x=100,y=100
 Copied   = x=100,y=100
 Original = x=200,y=200
 Copied   = x=100,y=100

All you need to do here is:
  • Ensure that all classes in the object's graph are serializable.
  • Create input and output streams.
  • Use the input and output streams to create object input and object output streams.
  • Pass the object that you want to copy to the object output stream.
  • Read the new object from the object input stream and cast it back to the class of the object you sent.

In this example, I have created a ColoredCircle object, c1 and then serialized it (write it out to ByteArrayOutputStream). Then I deserialed the serialized object and saved it in c2. Later I modified the original object, c1. Then if you see the result, c1 is different from c2. c2 is deep copy of first version of c1. So its just a copy and not a reference. Now any modifications to c1 wont affect c2, the deep copy of first version of c1.

Well this approach has got its own limitations and issues:

As you cannot serialize a transient variable, using this approach you cannot copy the transient variables. 
Another issue is dealing with the case of a class whose object's instances within a virtual machine must be controlled. This is a special case of the Singleton pattern, in which a class has only one object within a VM. As discussed above, when you serialize an object, you create a totally new object that will not be unique. To get around this default behavior you can use the readResolve() method to force the stream to return an appropriate object rather than the one that was serialized. In this particular case, the appropriate object is the same one that was serialized.
Next one is the performance issue. Creating a socket, serializing an object, passing it through the socket, and then deserializing it is slow compared to calling methods in existing objects. I say, there will be vast difference in the performance. If your code is performance critical, I suggest dont go for this approach. It takes almost 100 times more time to deep copy the object than the way you do by implementing Clonable interface.

When to do shallow copy and deep copy?

Its very simple that if the object has only primitive fields, then obviously you will go for shallow copy but if the object has references to other objects, then based on the requiement, shallow copy or deep copy should be chosen. What I mean here is, if the references are not modified anytime, then there is no point in going for deep copy. You can just opt shallow copy. But if the references are modified often, then you need to go for deep copy. Again there is no hard and fast rule, it all depends on the requirement.

Finally lets have a word about rarely used option - Lazy copy

A lazy copy is a combination of both shallow copy and deep copy. When initially copying an object, a (fast) shallow copy is used. A counter is also used to track how many objects share the data. When the program wants to modify the original object, it can determine if the data is shared (by examining the counter) and can do a deep copy at that time if necessary.

Lazy copy looks to the outside just as a deep copy but takes advantage of the speed of a shallow copy whenever possible. It can be used when the references in the original object are not modified often. The downside are rather high but constant base costs because of the counter. Also, in certain situations, circular references can also cause problems.

posted on 2012-04-07 18:41 gembin 阅读(593) 评论(0)  编辑  收藏 所属分类: JavaSE


















Design Pattern


Favorite Links


Game Dev


Identity Management

IT resources






Version Control







free counters