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

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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major 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

      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.

        1. WFLY5962test.zip
          3 kB

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

                Created:
                Updated:
                Resolved: