Is automatic dirty checking of directly accessed fields supposed to work in Hibernate? Even when Hibernate uses a proxy?

Example pseudocode:


This code doesn't update the cat record for me. While stepping through in a debugger it seems that Hibernate create a proxy for cat, the name field of the cat proxy is indeed set, but commit doesn't even check for a dirty object because it thinks the session is empty (PersistenceContext.hasNonReadOnlyEntities= true).

If I replace load() with get() in the above code (which does NOT instantiate a proxy), then it works as expected, it updates the record.

Hibernate version: 3.0beta4

Mapping documents: Class with access="field"


[/code]

You set an instance variable of the proxy. Not of the entity instance.

Don't use direct access to public instance variables in Hibernate (or OO in general).

thank you very much. It might worth to mention this in the doc or in the book. (I understand that it is reasonable to think that public fields is not OO enough, but if I am developing an application (not a library), trivial getters and setters has no benefit but only disadvantage: getCount() is less readable then count or even count(), more code, more members displayed in the IDE - and in the rare case when I indeed find later that I need some logic in the getter or the setter, it tooks only 10 seconds to refactor field access to getters setters using an IDE like Eclipse)