Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-5962

ServletContainerInitializers from jboss-deployment-structure.xml module dependencies are not invoked

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 10.0.0.Final
    • 10.0.0.CR5
    • Web (Undertow)
    • None
    • Hide

      -Add "com/redhat/testSCI" contents to $EAP_HOME/modules/system/layers/base
      -Deploy SCItest.war
      -This should produce a message like "Initializer invoked for ..."

      Show
      -Add "com/redhat/testSCI" contents to $EAP_HOME/modules/system/layers/base -Deploy SCItest.war -This should produce a message like "Initializer invoked for ..."
    • Workaround Exists
    • Hide

      The SCI is properly invoked if included in a global module, in the deployment itself, or in a deployment overlay

      Show
      The SCI is properly invoked if included in a global module, in the deployment itself, or in a deployment overlay

    Description

      If a module includes a ServletContainerInitializer, that ServletContainerInitializer is not invoked for any applications that include the module in its jboss-deployment-structure.xml module dependencies. It looks like the ServletContainerInitializerDeploymentProcessor only checks server provided dependencies.

      Attachments

        Issue Links

          is incorporated by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-2744 ServletContainerInitializers from jboss-deployment-structure.xml module dependencies are not invoked

          • 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.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-5159 Failed to deploy war in EAP 7.0.0, error shows "Duplicate Filter registration for ..."

          • 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.
          • Verified

          Activity

            People

              sdouglas1@redhat.com Stuart Douglas
              rhn-support-aogburn Aaron Ogburn
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: