[
https://issues.jboss.org/browse/WFLY-12290?page=com.atlassian.jira.plugin...
]
André Kornetzky updated WFLY-12290:
-----------------------------------
Workaround Description:
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>}}
Workaround: Workaround Exists
Priority: Minor (was: Major)
Class ava.net.HttpClient not found in Wildfly 17
------------------------------------------------
Key: WFLY-12290
URL:
https://issues.jboss.org/browse/WFLY-12290
Project: WildFly
Issue Type: Bug
Affects Versions: 17.0.1.Final
Environment: Development: Win 10, JDK 11, Eclipse 2019-06
Reporter: André Kornetzky
Assignee: Brian Stansberry
Priority: Minor
Labels: Modules, jdk11
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/fc649ab01eff81c55084d241fb...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)