Europa Computer ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMDMzZWVlMmVk... ) / New Feature ( https://hibernate.atlassian.net/browse/HHH-16996?atlOrigin=eyJpIjoiMDMzZW... ) HHH-16996 ( https://hibernate.atlassian.net/browse/HHH-16996?atlOrigin=eyJpIjoiMDMzZW... ) Config property to allow using a custom BytecodeProvider ( https://hibernate.atlassian.net/browse/HHH-16996?atlOrigin=eyJpIjoiMDMzZW... ) Change By: Europa Computer ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) On a legacy project @Entity are used as DTOs and exported to the client through ejb remoting with wildfly. Lazy properties that are not used by the client are not initialized (and not being used a LazyInitializationException is not thrown) Everything worked until 6.1. Since 6.2 a change has been introduced in SerializableProxy.java where a sessionFactory is required in the readResolve, which is not used on the client side. How can I now deserialize entities with uninitialized proxies without having to change all the server-side code? *Commit that change the old functioning* The global {{BytecodeProvider}} instance was removed as part of [[HHH-16058] - Hibernate JIRA 2|https://hibernate.atlassian.net/browse/HHH-16058] on purpose by @Sanne Grinovero. *Possible solution* Introduce some sort of config property to allow using a global {{BytecodeProvider}} for this use case. ( https://hibernate.atlassian.net/browse/HHH-16996#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16996#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#100233- sha1:63d45e1 )