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

Steve Ebersole ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16096 ( https://hibernate.atlassian.net/browse/HHH-16096?atlOrigin=eyJpIjoiYmVkMj... ) Re: Passing an ExtendedBeanManager which is notified too late leads to initialization error ( https://hibernate.atlassian.net/browse/HHH-16096?atlOrigin=eyJpIjoiYmVkMj... ) I don’t think they are. Your situation is a case of using the “extended” CDI strategy. When using either “extended” or “delayed”, beans other than converters and listeners will never use CDI. Your situation should never happen with my PR. And as you have no test attached it is hard to verify. You can try with my PR, wait for CR2 and try that or attach a test here. Depending on how easily consumable that test is, I may or may not be able to integrate it prior to release. ( 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 )