6.6.x regression - loading a JPA entity a second time when it contains composite key references can cause IllegalArgumentException in reflection code

I was able to remove the DocumentReceiver entity from the problem.

Improved the Diagram to make clear that Owner is not an Entity but an embeddable structure.
Entities:

• Document

• DocumentReceiver (Xref table)

• CorporationUser (Xref table)

• Person (extends abstract User)

• Corporation (extends abstract User)

Hint: when removing the embedded Owner class and move the fields into the Document class, the problem collapses.

So you are telling me I should write an extensive substack essay on why to abandon Hibernate JPA in any essential project that has more than 3 tables involved?

Look at the entity graph and tell me which one you think I should remove without collapsing the problem? Given that they are all essential in our productive code and it is your regression that stops us from upgrading?

I removed Lombok but again this is just syntactic sugar and does not contribute to the problem!

I understand that. But I need you to understand that we use the reproducer you submit as the basis for the test that goes into the Hibernate ORM test suite. And we don’t have (nor want) Lombok in our code.

Nor do we want a test with seven entities in it!

So look, what I’m hearing from you is that this issue is not very important to you, at least not important enough for you to do the work on your side, and so I can just close the issue. Is that correct?