|Re: [eclipselink-users] @Id ValidationException with EclipseLink - seenew bug# 240679 - 2nd workaround verification|
David,The problem only occurs with those entities do not define any mappings and that inherit the access type from a mapped superclass. In your case the entity class was incorrectly being defaulted to FIELD when it should have inherited the PROPERTY access from its mapped superclass.
Cheers, Guy----- Original Message ----- From: "David Nedrow" <dnedrow@xxxxxxx>
To: "EclipseLink User Discussions" <eclipselink-users@xxxxxxxxxxx> Sent: Monday, July 14, 2008 1:03 PMSubject: Re: [eclipselink-users] @Id ValidationException with EclipseLink - seenew bug# 240679 - 2nd workaround verification
On Jul 14, 2008, at 10:50 AM, MICHAEL.OBRIEN@xxxxxxxxxx wrote:David,For workaround 2 - use an orm.xml annotation, I verified the following change if you don't want to move your annotations to your fields and keep your entities as-is.Michael, Thanks for all the info. It's odd that it only manifests with two particular entities.All of my other entities are defined precisely the same way (annotation on the getId), and they work without a problem.-David _______________________________________________ eclipselink-users mailing list eclipselink-users@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipselink-users
Back to the top