Hi,

I have notice a problem where I have lets say a class

x.y.MyDataClass

and another classs lets call in

a.b.c.MyDataClass


both of these classes are mapped to a database table in hibernate config file.

Both of these work okay seperately.
But when they are used in same project they conflict even though the classes are fully qualified in the mapping file.

Renaming one of thes eg x.y.MyDataClass becomes x.y.YourDataClass

and it all works okay again.

Has anyone else seen this problem?

It looks like a hibernate bug to me.
I am in the process of testing this outside my application to check this.

Any ideas?
B

Solved it.
You need to set the autoImport=false in the hibernate mapping file

From the manual.
----
If you have two persistent classes with the same (unqualified) name, you should set auto-import="false". Hibernate will throw an exception if you attempt to assign two classes to the same "imported" name.
----

So
<hibernate-mapping auto-import="false">
<class name="x.y.MyData" table="MY_DATA_TABLE">


Hope this saves someone else some time.

B