Limitation of JPA 1.0 using @IdClass with *nested* composite primary keys?
Given the following example (departments - projects): A department has the following properties (composite primary key): @Entity @IdClass(DeptId.class) public class Department { @Id @Column(name="number") private Integer number; @Id @Column(name="country") private String country; @Column(name="name") p...