Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-2744

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

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.0.0.ER5
    • 7.0.0.ER3
    • Undertow
    • None
    • 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
    • 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 ..."

    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

          incorporates

          Bug - A problem that impairs or prevents the functions of the product. WFLY-5962 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. WFLY-9880 ServletContainerInitializer@onStartup is not invoked for deployment

          • 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

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: