Are you talking about non-aggregated composite ids? If so, the question is
not just about backwards compatibilty. This is a vendor specific feature
and the question becones whether that feature is still worthwhile.
On Jan 15, 2013 3:56 PM, "Brett Meyer" <brmeyer(a)redhat.com> wrote:
Up until now, we've always sided with backward compatibility,
even if it's
against the spec. We do have
https://hibernate.onjira.com/browse/HHH-7803to introduce
settings that would ease the restrictions. Should this fall
under that?
Brett Meyer
Red Hat Software Engineer, Hibernate
+1 260.349.5732
----- Original Message -----
From: "Gail Badner" <gbadner(a)redhat.com>
To: "hibernate-dev(a)lists.jboss.org hibernate-dev" <
hibernate-dev(a)lists.jboss.org>
Sent: Tuesday, January 15, 2013 3:29:08 PM
Subject: [hibernate-dev] Should Hibernate support @Id for embedded IDs
I've noticed that some failures using the new metamodel are due to
embedded IDs being annotated with @Id instead of @EmbeddedId.
Should Hibernate support this mapping?
Thanks,
Gail
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev