Hibernate Community • View topic

View unanswered posts | View active topics

Board index » Hibernate & Java Persistence » Hibernate Users

All times are UTC - 5 hours [ DST ]

SAVING Status

Page 1 of 1

[ 2 posts ]

Previous topic | Next topic

Author

Message

cmrudd

Post subject: SAVING Status

Posted: Thu Nov 03, 2005 9:28 pm

Beginner

Joined: Tue Aug 03, 2004 1:13 pm
Posts: 23

Hibernate version: 2.1.8
FlushMode = on commit

Im trying to trace down an issue im having with deserializing the session.
The code is greatly simplified but produces the same sequence as the production code.

I do the following :

Code:

  
// Session is already open

// A is a mapped object
S.saveOrUpdate( new A() ); 

// verify the session is dirty
assert( S.isDirty() ); 

// disconnect the session ( as we cant serialize a connected session )
S.disconnect();

// Serialize the session
Object state = doSerialize( S );

// Deserialize the session
S = (Session)doDeserialize( state ); 

I get a deserialization problem ( InvalidObjectException ) from net.sf.hibernate.impl.SessionImpl.Status. A status of "SAVING" was serialized out, but the readResovle doesnt allow that value to be read back in.

If i comment out the assert it works just fine (as no entity with state SAVING is serialized).

Is there some way to work around this?

Effectivly what i am doing is a long transaction by doing operations on a flush on commit session that is deserialized, modified based on the users input, disconnected and serialized into user state. IsDirty is used to determine if the user has made any changes (net of all the edits they have done. Ie changing a property then puting it back nets to no change). Then at some point the user indicates that they either want to discard all they have done or save it.

Top

cmrudd

Post subject: Correction....

Posted: Thu Nov 03, 2005 10:21 pm

Beginner

Joined: Tue Aug 03, 2004 1:13 pm
Posts: 23

Correction ( accidentally ommited the second part of the code )

Code:

// Session is already open 

// A is a mapped object 
S.saveOrUpdate( new A() ); 

// verify the session is dirty 
assert( S.isDirty() ); 

// disconnect the session ( as we cant serialize a connected session ) 
S.disconnect(); 

// Serialize the session 
Object state = doSerialize( S ); 

// Deserialize the session 
S = (Session)doDeserialize( state ); 

// reconnect the session
S.reconnect();
S.beginTransaction();

// locate the instance of a from the session
A a = (A)locateInstance( A.class, S )

B b = new B();

a.getChildren().add( b );

// verify the session is dirty 
assert( S.isDirty() ); 

// disconnect the session ( as we cant serialize a connected session ) 
S.disconnect(); 

// Serialize the session 
Object state = doSerialize( S ); 

// Deserialize the session 
S = (Session)doDeserialize( state ); 

A.children is a one-to-many list with cascade=all-delete-orphan

The exception occurs on the loading of the state for the instance of object B.

If I either:
a) comment out the second assert, or
b) add a call to S.saveOrUpdate( b ) the deserialize works correctly. (NOTE this is not viable to do in the appliation, but is mentioned inorder to diagnose the problem )

So it seems to be a problem with transient objects picked up by cascading.

Top

Page 1 of 1

[ 2 posts ]

Board index » Hibernate & Java Persistence » Hibernate Users

All times are UTC - 5 hours [ DST ]

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum