On 27 Jan 2014, at 15:17, Steve Ebersole <st...@hibernate.org> wrote:
> So this is another representation of a choice we are having to make quite a > bit in 5.0 development... correctness versus "legacy", which has really > implications for users. So if users are relying on this Hibernate "feature" > of splitting identifier mapping annotations between the entity and the > IdClass, their apps would break if we now start supporting this "the correct > way". > > Maybe this is another case where we can log warning for "misplaced" > annotations when we see an IdClass with persistence mapping annotations. +1 > The spec makes no mention of use cases where an IdClass has mapping > annotations, nor do I consider this a "usability feature" from the users > perspective (aside from the mentioned compatibility concerns). +1 —Hardy _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
