Hi All,


I am facing one problem, I have tried alll forums but did't get the solution.

Example:-

I have following classes: Person,CompanyDetails,Ocupation and tables: PERSON, COMPANY, COMPANY_DETAILS, OCCUPATION
Person class has following mapping :

<many-to-one name="ocupation" column="OCC_ID" lazy="false" not-null="true"/>

<set name="companyDetails" table="COMPANY" schema="x" lazy="false" fetch="join">
<key column="PERSON_OCC_ID" property-ref="ocupation">
<many-to-many class="com.company.CompanyDetails" column="DETAIL_ID">
</set>

Now my set which is company details , it points to a table COMPANY which has a column PERSON_OCC_ID which is a foregin key to PERSON table's OCC_ID(which is a non-primary key of PERSON table). SO, I am using property-ref in the key column. But this is giving ClassCastException, Becuase it's fetching Ocupation istead of CompanyDetails. If I remove property-ref it's comparing with the primary key of PERSON table, which is not my requirement

About this line:

<many-to-one name="ocupation" column="OCC_ID" lazy="false" not-null="true"/>

Shouldn't it hava a class attribute

About the column PERSON_OCC_ID: Is it also a foreign key to table OCCUPATION, or is only a property. In the second case, I think you are comparing an Occupation entity (The property ocupation), to wathever you have in the company table

Please, post also the mapping of the CompanyDetails class. That might help a lot.

About this line:

<many-to-one name="ocupation" column="OCC_ID" lazy="false" not-null="true"/>

if it is in the same package then I think it doesn't require it. Because it's working fine.


About the column PERSON_OCC_ID: It a foreign key to the table PERSON not OCCUPATION, But the only thing is this FOREIGN KEY refers to a non-primary key of PERSON table that is why I am companring it with the property occupation in the company table.


There is nothing important in the CompanyDetails class which can help you still I am posting the mapping for this

<id column="DETAIL_ID">
<property name="location" column="comp_location">
<property name="name" column="comp_name">

At database level a foreign key by definition has to reference a primary key or a unique constraint. However, at the ORM level I believe all references must be to the id property of the referenced entity, that is mapping of foreign keys based on unique constraints back into the ORM world is not supported. This is because an entity only has a single identity and a database level unique constraint is not be reflected at the entity level as an alternate id.