[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-4870) Cannot determine java-type from given member [null]

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4870?page=c... ] Andreas Joseph Krogh commented on HHH-4870: ------------------------------------------- Hi, thanks for looking into this. The nature of this mapping is that all Persons _may_ map to a Company, but the (nullable) FK in the database points to a UNIQUE key not being the @Id of "the other side". There are historical reasons for why the database is like this. Why is this association effectively a one-to-one mapping? I know it's not common to have a ManyToOne-relationship with an FK to a none-@Id column on the other side, but "companyId" (columnname="id") is a UNIQUE-key in Company and should work just fine, making this a certified @ManyToOne-relation AFAICT. This is the reason why "referencedColumnName" exists on the @JoinColumn annotation if I'm not misstaking. This worked fine with JPA1/Hibernate-3.3.2 and I believe I'm not the only person having this issue when upgrading to Hibernate-3.5. I certainly hope you find the time to fix this before going GA. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira