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

BeanDeploymentModules service only makes sense for Java EE environments

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 2.4.4.Final
    • 2.3.5.Final, 2.4.3.Final, 3.0.0.Final
    • None
    • None

    Description

      Right now, this service is registered for any non-SE environment - see also org.jboss.weld.bootstrap.WeldStartup.isEEModulesAwareEnvironment(). However, the integrator (e.g. PAX CDI) could provide its own org.jboss.weld.bootstrap.api.Environment implementation.

      For Weld 3 we should probably change the SPI, ie. add org.jboss.weld.bootstrap.api.Environment#isEEModulesAware() method with default implementation returning false and use this method in WeldStartup.

      For Weld 2 we should probably change the logic of WeldStartup.isEEModulesAwareEnvironment() to return false for any env which is not EE_INJECT, EE, SERVLET.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. WELD-2401 Regression in BeanDeploymentModules registration

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. WELD-2398 Environment should report if it is EE modules aware

          • 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
          relates to

          Bug - A problem that impairs or prevents the functions of the product. WELD-2077 BeanDeploymentModules service does not make sense for Weld SE

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: