Uploaded image for project: 'Hibernate ORM'
  1. Hibernate ORM
  2. HHH-10477

Setting to allow delayed access to CDI

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.1.0, 5.0.8
    • Component/s: None
    • Labels:
      None
    • Last commented by a user?:
      true

      Description

      HHH-8706 Closed defines the best case option for handling the chicken/egg problem between CDI and JPA using a specific notification event (as a BeanManager lifecycle event) that the BeanManager is ready for use.

      However, it is also possible to define a setting that allows telling Hibernate to delay access to the CDI BeanManager until it is needed on first use. There is some danger in this solution as it moves the throwing of potential exceptions that should fail the deployment until runtime after deployment has succeeded.

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                steve Steve Ebersole
                Reporter:
                steve Steve Ebersole
                Participants:
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - Not Specified
                  Not Specified
                  Logged:
                  Time Spent - 1.7h
                  1.7h