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

Class java.net.HttpClient not found in Wildfly 17

    XMLWordPrintable

Details

    • Hide

      Use the appropriate API from the JDK.

      Show
      Use the appropriate API from the JDK.
    • Workaround Exists
    • Hide

      Adding the Dependency in the maven-file works fine.

      {{<plugin>
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-war-plugin</artifactId>
      <version>2.3</version>
      <configuration>
      <archive>
      <manifestEntries>
      <Dependencies>java.net.http</Dependencies>
      </manifestEntries>
      </archive>
      </configuration>
      </plugin>}}

      Show
      Adding the Dependency in the maven-file works fine. {{<plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-war-plugin</artifactId> <version>2.3</version> <configuration> <archive> <manifestEntries> <Dependencies>java.net.http</Dependencies> </manifestEntries> </archive> </configuration> </plugin>}}

    Description

      When I deploy my war module, I get the following error:
      Caused by: java.lang.ClassNotFoundException: java.net.http.HttpClient from [Module "deployment.webservice-impl-1-3.0.0.war" from Service Module Loader]
      In the same environment is also a Wildfly 16.0.0 installed. There the war module starts without errors.

      In the discussion on https://developer.jboss.org/message/990207?et=watches.email.thread#990207 it was said that this was not considered by the upgrading of the JBoss module:
      https://github.com/wildfly/wildfly-core/commit/fc649ab01eff81c55084d241fb2c57e012830364#diff-23e5fdc1c637eca93f059ac5c61f51fb

      Attachments

        Issue Links

          incorporates

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFCORE-4753 Upgrade JBoss Modules from 1.9.1.Final to 1.9.2.Final

          • 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 caused by

          Bug - A problem that impairs or prevents the functions of the product. MODULES-392 java.se module doesn't take into account all modules that it "requires"

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

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-19697 [GSS](7.2.z) MODULES-392 - java.lang.ClassNotFoundException: java.net.http.HttpClient

          • 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

          Activity

            People

              ropalka Richard Opalka
              andre.kornetzky André Kornetzky (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: