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

Relative ordering of webfragments causes an IllegalStateException

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • 7.1.0.DR7
    • None
    • Undertow
    • None
    • 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
    • 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.

    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

          clones

          Bug - A problem that impairs or prevents the functions of the product. WFLY-7163 Relative ordering of webfragments causes an IllegalStateException

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: