From f653e26a49b357788713245bed21eaeafcf619ca Mon Sep 17 00:00:00 2001 From: Steve Ebersole Date: Thu, 7 Sep 2017 12:01:51 -0500 Subject: [PATCH] improve documentation (Javadoc) of org.hibernate.cfg.AvailableSettings.CDI_BEAN_MANAGER --- .../main/java/org/hibernate/cfg/AvailableSettings.java | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/hibernate-core/src/main/java/org/hibernate/cfg/AvailableSettings.java b/hibernate-core/src/main/java/org/hibernate/cfg/AvailableSettings.java index 96541aad1b..a8a12c0e68 100644 --- a/hibernate-core/src/main/java/org/hibernate/cfg/AvailableSettings.java +++ b/hibernate-core/src/main/java/org/hibernate/cfg/AvailableSettings.java @@ -175,6 +175,15 @@ public interface AvailableSettings { /** * Used to pass along the CDI BeanManager, if any, to be used. + * + * According to JPA, strictly, the BeanManager should be passed in + * at boot-time and be ready for use at that time. However not all + * environments can do this (WildFly for one). To accommodate such + * environments, Hibernate provides an SPI via + * {@link org.hibernate.jpa.event.spi.jpa.ExtendedBeanManager} that + * can be used to provide delayed BeanManager access. Long story + * short, this setting could be typed as BeanManager or as + * {@link org.hibernate.jpa.event.spi.jpa.ExtendedBeanManager}. */ String CDI_BEAN_MANAGER = "javax.persistence.bean.manager";