Hi,

when I attempt to delete an object, Hibernate throws a ConstraintViolationException which is expected behaviour due to database referential integrity constraints. However, when I then attempt to refetch this object in the same session via get or load an "ObjectDeletedException: The object with that id was deleted" is thrown. However, if the session is closed and then reopened I can find the object via get or load.

Is the above expected behaviour not being able to get the object after the ConstraintViolationException, or is it a bug?


thanks.

if you encounter an exception you should close that session, not performing more operations within it.



from http://www.hibernate.org/168.html

Jaime,

Its actually in the transaction.commit() which is throwing the ConstraintViolationException - not the session. Could you point me to where you read that documentation - as the API doco for Session says the session should be closed, but I couldnt find anything relating to closing the session if the transaction throws an exception?

Given the 'open session in view' pattern I wouldnt think we should have to close the session because of this? I'm trying to refetch the object outside of the transaction in the same session.

To me, this problem still smells of a bug???


thanks.

i already posted the link...

http://www.hibernate.org/168.html

you need to roll back the transacation and close the session...