Uploaded image for project: 'Thorntail'
  1. Thorntail
  2. THORN-918

JBossWebContainer.setDefaultContextRoot vs. custom jboss-web.xml inside the default deployment

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2017.1.1
    • Component/s: None
    • Labels:
      None
    • Sprint:
      2016-Dec-B

      Description

      When creating the default deployment, DefaultWarDeploymentFactory (and hence also DefaultJAXRSWarDeploymentFactory) end up calling JBossWebContainer.setDefaultContextRoot as a part of the WARArchiveImpl (resp. JAXRSArchiveImpl) constructor.

      If the deployment file contains custom jboss-web.xml file, the setting of the default context root is then nullified. But Swarm isn't aware of that, and Swarm Arquillian container still injects / to @ArquillianResource URL fields, even if the application is actually present on /deployment-name.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  bob.mcwhirter Bob McWhirter
                  Reporter:
                  lthon Ladislav Thon
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: