Details
-
Type:
Bug
-
Status:
Closed
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.2
-
Component/s: None
-
Labels:None
-
JDK version and platform:1.4.2_10 for Windows
Description
If object implements readResolve() method it is called twise: once before the attributes are assigned and once after.
This is different from Sun Serialization specification. The readResolve should be called only once after object is fully constructed and all values assigned.
Here is the quote from Sun Serialization specification:
"The readResolve method is not invoked on the object until the object is fully
constructed"
Issue Links
- is depended upon by
-
XSTR-317
XStream 1.2 release coordination.
-
Activity
I found a situation, where this could happen. Basically all serializable objects with such a method where affected, that also have an unserializable parent. You might try the latest snapshot for your case and report.
Show
Jörg Schaible
added a comment - I found a situation, where this could happen. Basically all serializable objects with such a method where affected, that also have an unserializable parent. You might try the latest snapshot for your case and report.
Jörg Schaible
added a comment - I found a situation, where this could happen. Basically all serializable objects with such a method where affected, that also have an unserializable parent. You might try the latest snapshot for your case and report. 
Hi Dimitry,
we have a unit test, that ensures, that this normally does not happen: http://fisheye.codehaus.org/browse/xstream/trunk/xstream/src/test/com/thoughtworks/acceptance/SerializationCallbackOrderTest.java?r=797
So can you elaborate more about the circumstances, where this happens for you or - even better - provide a test case?