[hibernate-issues] [JIRA] (HHH-16096) Passing an ExtendedBeanManager which is notified too late leads to initialization error

Vedran Prišćan ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63d101b... ) *commented* on HHH-16096 ( https://hibernate.atlassian.net/browse/HHH-16096?atlOrigin=eyJpIjoiZWY2Mz... ) Re: Passing an ExtendedBeanManager which is notified too late leads to initialization error ( https://hibernate.atlassian.net/browse/HHH-16096?atlOrigin=eyJpIjoiZWY2Mz... ) I did write a test in the commit: https://github.com/hibernate/hibernate-orm/pull/6018/commits/69ea77de8c43... ( https://github.com/hibernate/hibernate-orm/pull/6018/commits/69ea77de8c43... ) I agree that with your solution this should not happen, but for consistency with BeanImpl there should also be a null check in NamedBeanImpl. Or we can remove both null checks if it can never happen anymore, but I prefer there is one. ( https://hibernate.atlassian.net/browse/HHH-16096#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16096#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#100214- sha1:3d33cb1 )