Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNGJhZGZjNWVi... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-15450?atlOrigin=eyJpIjoiNGJhZG... ) HHH-15450 ( https://hibernate.atlassian.net/browse/HHH-15450?atlOrigin=eyJpIjoiNGJhZG... ) Add fluent style access type ( https://hibernate.atlassian.net/browse/HHH-15450?atlOrigin=eyJpIjoiNGJhZG... ) Issue Type: Improvement Assignee: Unassigned Components: hibernate-core Created: 16/Aug/2022 05:54 AM Priority: Major Reporter: Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) The “fluent” style is to not have prefixes for method names. Every no-arg non-void method is considered a property. A single arg void method with the same name and argument type matching the read accessor type, is considered to be the write accessor. For example: @Entity @Access(FLUENT) public class Blog { ... public String title() {...} public void title( String title) {...} } It might be worth considering same named single argument methods also as write accessors, regardless of the return type, to support use cases where the write accessor returns the “this” object for chained method invocation. ( https://hibernate.atlassian.net/browse/HHH-15450#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15450#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#100204- sha1:f005d5a )