Hi,
I have a mapping that looks like this



i get a
Caused by: : Repeated column in mapping for entity: MyObject column: DEF_ID (should be mapped with insert="false" update="false")

even if i put insertable and updatable to false i get the same error
what should i do?

You've defined the relationship to MyObject as OneToMany from both Parent and Child but used the same join column name (DEF_ID). You need 2 different join column names - one for the relationship between MyObject to Parent and one for MyObject to Child.

I guess you're right. But i'd like to elaborate my problem a little further.

There are several modules in my project that use "MyObject" in a OneToMany relation and MyObject has been defined with custom ddl statements so that the join column is not a foreign key but is barely another non-nullable column.
The ids that go into the "DEF_ID" column are Unique so that hibernate can identify the objects uniquely.

Funny thing is that multiple entities that point to MyObject work in real time scenarios (ie in Tomcat) where all the entities are in the same sessionFactory. But only during Unit Testing where ONLY 2 objects (ie Parent and Child) point to the same MyObject that a failure occurs.

One more thing: The unique id generator for the entities is a custom generator that is used.

i also tried another thing



and now i get something like

: Duplicate property mapping of _listObjectsBackref found



is there another way in which i dont create the MyObjects table through hibernate and indicate that i am going to be storing unique ids into the DEF_ID column so that hibernate can get back to my parent object?

Ok.
Here's clarifying the situation once again.

Apparently no other module was using the MyObject class and hence it was not crashing during Tomcat deployment. So i was mistaken here.

But nevertheless i found a solution to the problem
When hbm2dll had been turned on, hibernate went and created 2 foreign key associations on "DEF_ID" to the 2 parents that would associate with it. So if one parent would insert into MyObject.class table, it would start crying by saying that there has been a foreign key violation. (because the other parent does not have an Id that matches that of the first parent. )

So the solution was to turn off hbm2ddl and not have any foreign key constraint on the JoinColumn and also to make the column "nullable" so that it would trick hibernate to believe that even though 2 or more parents join on the same column, the parents would insert a null value into the "DEF_ID" column whereby "supposedly existent multiple foreign key constraints" would not throw exceptions.

Has anybody seen this mapping called, @Any
I guess its a short cut soln to all that i was talking about earlier :)

Drat. I should have found this annotation sooner!