Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15977 ( https://hibernate.atlassian.net/browse/HHH-15977?atlOrigin=eyJpIjoiNDM0NG... ) Re: Deprecate @Persister ( https://hibernate.atlassian.net/browse/HHH-15977?atlOrigin=eyJpIjoiNDM0NG... ) The better way to do that would be through generated values. For an update or creation date/time that is super easy and Hibernate will even handle setting the value for you - see @CreationTimestamp or @UpdateTimestamp For the user, whether generated values will work depends a bit on how you know the user to set. Considering you had access to that information inside a custom persister, I’m guessing you’d have access to it inside a custom BeforeExecutionGenerator ` as well. If not, a custom event listener or Interceptor would work. ( https://hibernate.atlassian.net/browse/HHH-15977#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15977#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#100217- sha1:45db922 )