[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4861?page=c... ] Emmanuel Bernard commented on HHH-4861: --------------------------------------- I think you have a point, Person should really be the type. That being said, the derived identity takes a different approach in which the java type of the associated entity is considered the or part of the pk section 2.4.1.1 sums it up. Here is an extract for "simple pks". If the dependent entity has a single primary key attribute (i.e, the relationship attribute or an attribute that corresponds to the relationship attribute) and the primary key of the parent entity is a simple pri- mary key, the primary key of the dependent entity is a simple primary key of the same type as that of the parententity(andneitherEmbeddedIdnorIdClassisspecified). Inthiscase,either(1)therela- tionship attribute is annotated Id, or (2) a separate Id attribute is specified and the relationship attribute is annotated MapsId (and the value element of the MapsId annotation is not specified). -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4861?page=c... ] Steve Ebersole updated HHH-4861: -------------------------------- Assignee: Steve Ebersole Component/s: (was: annotations) entity-manager core Summary: Allow lookup by the "simple" pk type of "parent entity" in derived identities" cases (was: The primary key type of a derived identity is not correct) -- 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