I think there is a bug on the many-to-one relationship when lazy is set to true.

Hibernate version: 3.1.3

Mapping documents:

Name and version of the database you are using:
mysql 4.1

The class Community extends an abstract class AbstractPersistentable that has the uid, state and creationDate attribute. The uid is generated on the constructor of the object.

The problem is on the many-to-one relationship. All the objects and collections comes with its correct UID. But when the object on the many-to-one relation is initialized the UID is not set. This means the object has a different id from the one in the database. If the many-to-one relation is lazy=false the id is set correctly. And notice the default-access=field. All other attributes is set correctly, but the uid stays the one generated in the constructor. A different one every time.

I think this is a bug from hibernate. Any clues?? Theres nothing wrong with the classes. I have at least three classes with this kind of relation and all many-to-one relation when initialized keeps the wrong id.

THANKS!

[/code]

Sounds like you're using member fields, rather than accessors. All uses of uid, even within the Community class, must go via accessors. The only methods allowed refer to the member fied are the accessor and mutator. This applies to all members of all mapped classes (assuming that you're using the property proxying method, rather than field). hashCode and equals are the methods that most frequently fall victim to this mistake.

I'm sorry, but I don't think I undestand what you said. This means I should never use field access?! Hibernate's documentation doesn't mention any problemns with that kind of access. And I dont have any problemns as I said in my post. Just with the many-to-one relationship and only when it's lazy=true.

So, can you explain better what's the problemn??

Thanks!

Yes, if you're using the normal access level (property), you should never use field access except in the getter and setter methods. This includes inside the equals() and hashCode() methods. Hibernate's docs mention this in a roundabout way, and I think they should make it clearer, but there you go. Here's one of way it's mentioned.

Section 19.1, "Fetching Strategies":

This is the default for access="property", the default.


This is the default for access="field", which presumably you have not turned on.

I think that the documentation for access and default-access should describe their effects on user code as well as on hibernate code, because it does not emphasize the potential pitfalls enough.. imo.

Thank you very much!!
Now it's clearer hehe