Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16572 ( https://hibernate.atlassian.net/browse/HHH-16572?atlOrigin=eyJpIjoiOGY4ZD... ) Re: jpa/core/query/flushmode TCK test failures ( https://hibernate.atlassian.net/browse/HHH-16572?atlOrigin=eyJpIjoiOGY4ZD... ) The underlying problem is pretty bad. The enhancement assumes that the field name always matches the “attribute name”, which is not necessarily true for PROPERTY access. The test in question, e.g., defines this entity: @Entity public static class Spouse { ... private String last; @Id Integer getId() {...}; String getLastName() {...}; void setLastName( String name) {...}; } Here, we have PROPERTY access (placement of @Id ) and thus a persistent attribute named lastName. The enhancement code however basis this decision on the field-name assuming it is the same thing as the attribute name. Here, it is (perfectly legally) not. Rafael Winterhalter ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) or any other ByteBuddy experts have thoughts on this? ( https://hibernate.atlassian.net/browse/HHH-16572#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16572#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#100225- sha1:b79b7f6 )