Uploaded image for project: 'Weld'
  1. Weld
  2. WELD-2429

Ensure that RI beans behave correctly even if initializeAfterBeanDiscovery() is not called

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • 3.0.2.Final, 2.4.6.Final
    • None
    • None
    • None

      If the non-portable mode is enabled, it should be possible to create and inject beans before AfterDeploymentValidation event is fired. This in itself is incorrect CDI SPI usage (see for example CDI-700 and CDI-718). However, we should ensure that RI beans behave "correctly" even if RIBean.initializeAfterBeanDiscovery() is not called yet, i.e. work only with the information available or throw a DefinitionException with a clear explanation.

              manovotn Matěj Novotný
              mkouba@redhat.com Martin Kouba
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: