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

Regression in BeanDeploymentModules registration

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 2.4.5.Final
    • 2.4.4.Final
    • None
    • None

      Weld 2.4.4.Final causes test failures on WFLY. The test is an EAR without WAR but it has a library and one EJB jar; both of these observe @Initialized(AppplicationScoped.class). See WFLY-3334 for more information on that.

      The real problem is that we have introduced a stricter check in WELD-2389 and only register a module if an integrator implements our Environments API by adding exactly same set of services. However, this is not the case with WildFly - see WildFlyWeldEnvironment (transaction services are missing in order to make it EE environment). As a result of that, Weld fails to register a non-web module (and therefore doesn't fire those events for it later on).

      So there are two options here:

      1. Revert the change in Weld and go back to lenient check to permit this behaviour.
      2. Change code on WildFly side and try to "correct" this
        • Might require special handling in regard to Swarm

              Unassigned Unassigned
              manovotn Matěj Novotný
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: