Multiple id properties without identifier type depends on the order in which entity mappings are processed
Description
Suppose we have the following entities:
When the above entities are added to the annotated classes list in the order
then the exception is thrown when the mappings are processed:
However, when the order is
everything works ok.
Also, if the Friendship mapping is changed by adding explicit referencedColumnName to the requester and friend fields, everything works ok regardless of the order in which the entities are added to the annotated classes list:
Attachments
1
Activity
Show:
Steve Ebersole October 28, 2015 at 3:25 AM
As part of verifying that this issue affects 5.0, please just set the "Affects version". Leave the "verify-affects-5.0" label and leave the issue in "Awaiting Response" status; these are critical for us to be able to track these verifications and triage them. Thanks.
Steve Ebersole October 27, 2015 at 7:16 PM
This bug report does not indicate that the reported issue affects version 5.x. Versions prior to 5.x are no longer maintained. It would be a great help to the Hibernate team and community for someone to verify that the reported issue still affects version 5.x. If so, please add the 5.x version that you verified with to the list of affected-versions and attach the (preferably SSCCE) test case you used to do the verification to the report; from there the issues will be looked at during our triage meetings.
Suppose we have the following entities:
When the above entities are added to the annotated classes list in the order
then the exception is thrown when the mappings are processed:
However, when the order is
everything works ok.
Also, if the Friendship mapping is changed by adding explicit referencedColumnName to the requester and friend fields, everything works ok regardless of the order in which the entities are added to the annotated classes list: