public Interface ManagedBeanSettings

Controls whether Hibernate can try to create beans other than converters and listeners using CDI. Only meaningful when a CDI container is used.

By default, Hibernate will only attempt to create converter and listener beans using CDI.

Since

6.2

Identifies a org.hibernate.resource.beans.container.spi.BeanContainer to be used.

Note that for CDI-based containers setting this is not necessary - simply pass the jakarta.enterprise.inject.spi.BeanManager to use via CDI_BEAN_MANAGER and optionally specify DELAY_CDI_ACCESS. This setting useful to integrate non-CDI bean containers such as Spring.

Since

5.3

Used in conjunction with hibernate.resource.beans.container when CDI is used.

By default, to be JPA spec compliant, Hibernate should access the CDI jakarta.enterprise.inject.spi.BeanManager while bootstrapping the org.hibernate.SessionFactory. In some cases however this can lead to a chicken/egg situation where the JPA provider immediately accesses the BeanManager when managed beans are awaiting JPA PU injection.

This setting tells Hibernate to delay accessing until first use.

This setting has the decided downside that bean config problems will not be done at deployment time, but will instead manifest at runtime. For this reason, the preferred means for supplying a CDI BeanManager is to provide an implementation of org.hibernate.resource.beans.container.spi.ExtendedBeanManager which gives Hibernate a callback when the BeanManager is ready for use.

Since

5.0.8

Used to pass a CDI jakarta.enterprise.inject.spi.BeanManager to Hibernate.

According to the JPA specification, the BeanManager should be passed at boot time and be ready for immediate use at that time. But not all environments can do this (WildFly, for example). To accommodate such environments, Hibernate provides two options:

1. A proprietary CDI extension SPI (which has been proposed to the CDI spec group as a standard option) which can be used to provide delayed BeanManager access: to use this solution, the reference passed as the BeanManager during bootstrap should be typed as org.hibernate.resource.beans.container.spi.ExtendedBeanManager.
2. Delayed access to the BeanManager reference: here, Hibernate will not access the reference passed as the BeanManager during bootstrap until it is first needed. Note, however, that this has the effect of delaying the detection of any deployment problems until after bootstrapping.

See Also

org.hibernate.boot.SessionFactoryBuilder#applyBeanManager(Object)