[hibernate-issues] [JIRA] (HHH-15660) Make use of ReflectionOptimizer in more cases

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiODRjYWUwODFl... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-15660?atlOrigin=eyJpIjoiODRjYW... ) HHH-15660 ( https://hibernate.atlassian.net/browse/HHH-15660?atlOrigin=eyJpIjoiODRjYW... ) Make use of ReflectionOptimizer in more cases ( https://hibernate.atlassian.net/browse/HHH-15660?atlOrigin=eyJpIjoiODRjYW... ) Issue Type: Improvement Affects Versions: 6.1.5 Assignee: Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Components: hibernate-core Created: 03/Nov/2022 02:55 AM Fix Versions: 6.1.6 Priority: Major Reporter: Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Right now, there is code that prevents using the ReflectionOptimizer for some entities. Specifically, entities that use FIELD access or have a virtual id a.k.a. identifierMapper. I totally understand that we have to opt-out of the optimizer for certain unknown PropertyAccess types in org.hibernate.metamodel.internal.EntityRepresentationStrategyPojoStandard#resolveReflectionOptimizer , but the two that I mentioned so far definitely shouldn’t cause that. I think that the fix might involve setting fields directly in the generated ReflectionOptimizer implementation, whereas right now, we always call setters ( org.hibernate.bytecode.internal.bytebuddy.BytecodeProviderImpl.SetPropertyValues ). ( https://hibernate.atlassian.net/browse/HHH-15660#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15660#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100210- sha1:a51bb46 )