I tried to submit the bug that when i call update on object with null version property the NPE is thrown.

The bug was closed by Gavin King 'cause with explanation "You cannot call update() on an object with a null version property. By definition."

And I would like to ask, why for update it is not by definition permited and delete throws very nice PropertyValueException?? I thing that the exception thrown by Hibernate are very different method by method and especially flushing throws exceptions, that nobody known which object the problem caused (I like very much the one with message ending "row not found").

Thanks for answer.

Jirka

For the exception return, you should think of what happen if you update a delete object in a DB.

You cannot uddate an optimistic locked object if you don't provide the optimistc locking informations, otherwis you'd break the semantic.

I dont't understand how your reply correlate to my question, why delete and update behave different?

I think that update and delete should behave the same way to updating and deleteing non-existed DB object (row).