Thanks for verifying and the test case, I’ll take a deeper look when I find some time.

Yes:

Fails as well…

Could you try one more thing, rename the getter and setter to getScore and setScoreas that is the name that is required by the spec AFAIU.

Thanks for checking.

I tried without these artificial PK class xetters:

Same result when running the gradle tests:

Fail.

According to the JPA specification section 2.4.1.1 something similar should indeed be possible. I’m citing the section here:

The names of the attributes of the id class and the Id attributes of the dependent entity class
must correspond as follows:
• The Id attribute in the entity class and the corresponding attribute in the id class must
have the same name.
• If an Id attribute in the entity class is of basic type, the corresponding attribute in the
id class must have the same type.
• If an Id attribute in the entity is a many-to-one or one-to-one relationship to a parent
entity, the corresponding attribute in the id class must be of the same Java type as the
id class or embedded id of the parent entity (if the parent entity has a composite primary
key) or the type of the Id attribute of the parent entity (if the parent entity has a
simple primary key).

Maybe the JPA TCK does not assert this, which would be unfortunate. I see this being specifically mentioned in the section 2.4.1.3 so you are right, it should work. What bugs me is that you have additional getters and setters. Have you tried removing the getGameId and getHomemethods from the id class already? I’m not sure if that is allowed. At least I don’t see it being specified in the JPA spec.