Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-4266

Classes for newer versions are not loaded from Multi-Release-JARs in WARs

    XMLWordPrintable

Details

    • Hide
      • Deploy buggywar.war to wildfly running on Java 11
      • Open http://localhost:8080/buggywar/Bla
      • The text should be "BlaBla(joined with Java 11)" but is "BlaBla(joined with Java 8)"

      You can verify the working multi-release-JAR by running "java -jar multireleaselib-0.0.1-SNAPSHOT.jar Bla 2" on Java 8 and Java 11

      Show
      Deploy buggywar.war to wildfly running on Java 11 Open http://localhost:8080/buggywar/Bla The text should be "BlaBla(joined with Java 11)" but is "BlaBla(joined with Java 8)" You can verify the working multi-release-JAR by running "java -jar multireleaselib-0.0.1-SNAPSHOT.jar Bla 2" on Java 8 and Java 11
    • 53300848

    Description

      1
      down vote
      favorite

      Since Java 9 there are Multi-Release JARs (MRJARS) that allow different classes for different Java versions to be included in one JAR file. I was surprised when a Wildfly 14 running on Java 11 executed Java-8-code in a JAR included in a WAR although the JAR was a MRJAR with code for Java 11. That JAR included as a dependency for a regular Java SE project is running different code depending on the running JRE, but when included in a WAR, the Java-11-code seems to be ignored.

      Is that expected behavior for a webserver, as Java EE 8 does not explicitly require Java 9 (which introduced MRJARs) but only Java 8?

      Attachments

        2. buggywar.war
          8 kB
          Daniel Schwering

        Issue Links

          is incorporated by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-16624 [GSS](7.2.z) JDK 11 Multi-Release jars - Classes for newer versions are not loaded and VFSResourceLoader doesn't take into account the Multi-Release manifest attribute value

          • 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.
          • Verified
          relates to

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-4298 Multi-release jar resource loading in VFSResourceLoader doesn't take into account the Multi-Release manifest attribute value

          • 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.
          • Resolved

          Activity

            People

              dlloyd@redhat.com David Lloyd
              hd42_jira Daniel Schwering (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: