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

Relative ordering of webfragments causes an IllegalStateException

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • 11.0.0.Alpha1
    • 9.0.2.Final, 11.0.0.Alpha1
    • Web (Undertow)
    • None
    • Hide

      Deploy a war containing 3 jars with webfragments using relative ordering. The initial order is based on the keys (jar name) of a hashset. In this scenario with 3 webfragments there are 6 possible initial orderings, based on the hash of the jar name. In 1 out the the 6 initial orderings WarMetaDataProcessor crashes.

      Show
      Deploy a war containing 3 jars with webfragments using relative ordering. The initial order is based on the keys (jar name) of a hashset. In this scenario with 3 webfragments there are 6 possible initial orderings, based on the hash of the jar name. In 1 out the the 6 initial orderings WarMetaDataProcessor crashes.
    • Hide

      override the relative ordering of the webfragments with an absolute ordering in the web.xml of the war

      Show
      override the relative ordering of the webfragments with an absolute ordering in the web.xml of the war

    Description

      Caused by: java.lang.IllegalStateException: WFLYUT0047: Relative ordering conflict with JAR: <jarname>.jar
      at org.wildfly.extension.undertow.deployment.WarMetaDataProcessor.resolveOrder(WarMetaDataProcessor.java:717)
      at org.wildfly.extension.undertow.deployment.WarMetaDataProcessor.deploy(WarMetaDataProcessor.java:212)
      ... 6 more

      Attachments

        Issue Links

          Activity

            People

              sdouglas1@redhat.com Stuart Douglas
              sboschman Sverre Boschman (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: