We might want to consider how to make that the default, as well.

We could have a configuration property (“use the FLUENT access type instead of PROPERTY by default” = true, “).

We could also try to emulate the current mechanism based on @Id: on an entity, if the @Id annotation is found on a method that doesn’t follow the JavaBeans naming conventions (e.g. Long id()), then we would default to the FLUENT access type. There are multiple challenges, though:

• No idea how this would work on mapped superclasses that don’t include an ID, but I suspect we have the same problem with the current access type (no way to decide on a default).
• What if I have a property in the fluent style that happens to also match JavaBeans conventions, e.g.`getDoneFast`? (boolean getDoneFast; public boolean getDoneFast(); public boolean getDoneFast(boolean value);)