Closed GoogleCodeExporter closed 8 years ago
are you making a defensive copy of your object before caching it? There is a
change that you're modifying the cached object, i.e. code holds a reference to
the object which is in the cache too.
Original comment by kostas.k...@googlemail.com
on 23 Dec 2013 at 3:25
I am not making any copy before caching the object..it is required? What is
defensive copy? It there any method in this jar which can do this?
Original comment by debrajpa...@gmail.com
on 24 Dec 2013 at 7:36
well, you might need to do a copy (using deepClone) of the object before
caching as well as after caching to avoid something like:
A a=new A();
cache(a);
a.setX(x); // the cached object was altered
Original comment by kostas.k...@googlemail.com
on 24 Dec 2013 at 5:28
Took a completely different approach of loading it first time through a job
which solved the issue.
Original comment by debrajpa...@gmail.com
on 3 Feb 2014 at 1:26
Original comment by kostas.k...@googlemail.com
on 3 Feb 2014 at 5:54
Original issue reported on code.google.com by
debrajpa...@gmail.com
on 23 Dec 2013 at 3:15