natural id can't be apply to component
Description
Activity

Christian BeikovApril 8, 2022 at 4:42 PM
Since no test case was provided for years, I'll close this issue as out of date. I also believe it will most probably not be an issue any more in 6.0.
If this still is an issue for you, please create a new issue with a test case that reproduces the problem.
Steve EbersoleOctober 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 EbersoleOctober 27, 2015 at 7:15 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.
For details, see http://in.relation.to/2015/10/27/great-jira-cleanup-2015/

Strong LiuJune 27, 2012 at 9:19 AM
this can be reproduced by org.hibernate.test.naturalid.immutableentity.ImmutableEntityNaturalIdTest#testImmutableNaturalIdLifecycle with moving the org.hibernate.test.naturalid.immutableentity.Building natural id properties to a component
org.hibernate.tuple.entity.EntityMetamodel#EntityMetamodel only checks if the property is a natural id or not, but it doens't take care of the property type, if the property is a component, then the org.hibernate.tuple.entity.EntityMetamodel#naturalIdPropertyNumbers is wrong, which causes exception be throwen at org.hibernate.event.spi.ResolveNaturalIdEvent#ResolveNaturalIdEvent due to "Entity [%s] defines its natural-id with %d properties but only %d were specified"