Uploaded image for project: 'CDI TCK'
  1. CDI TCK
  2. CDITCK-571

Test that BeanManager.createInstance() is only available after the deployment is validated

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 2.0.0.Final
    • 2.0.0.CR1
    • None
    • None

    Description

      The current spec wording allows to use BeanManager.createInstance() during AfterBeanDiscovery but that was obviously just an oversight (see also BeanManager.getReference() javadoc).

      Attachments

        Issue Links

          is related to

          Clarification - A clarification needed to a specification based on community feedback CDI-700 BeanManager.createInstance() shouldn't be allowed before AfterDeploymentValidation

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              tremes1@redhat.com Tomas Remes
              mkouba@redhat.com Martin Kouba
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                PagerDuty