[jboss-jira] [JBoss JIRA] (WFLY-12886) WELD-000119: Not generating any bean definitions from..class loading error: Type java.net.http.HttpClient

[nimo stephan (Jira)]

    [ https://issues.redhat.com/browse/WFLY-12886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13937905#comment-13937905 ] 

nimo stephan edited comment on WFLY-12886 at 12/19/19 5:29 AM:
---------------------------------------------------------------

Put the following class in a typcial war and start wildfly

{code:java}
import java.net.URI;
import java.net.http.HttpClient;
import java.net.http.HttpRequest;
import java.net.http.HttpResponse.BodyHandlers;
import java.time.Duration;
import java.util.Map;

import javax.ws.rs.client.Client;
import javax.ws.rs.client.ClientBuilder;
import javax.ws.rs.client.Entity;
import javax.ws.rs.client.Invocation;
import javax.ws.rs.client.WebTarget;
import javax.ws.rs.core.MultivaluedHashMap;
import javax.ws.rs.core.MultivaluedMap;
import javax.ws.rs.core.Response;

import org.jboss.logging.Logger;

public final class WebTool {

	private WebTool(){}
	
	private static Logger log = Logger.getLogger(WebTool.class);

	public static Response doPostRequest(Client httpClient, String uri, Entity<?> entity) {
		WebTarget target = httpClient.target(uri);
		Invocation request = target.request().buildPost(entity);
		return request.invoke();
	}

}
{code}

, then 
{code:java}
WELD-000119
{code}
 is shown in the log. If not, then use any static methods of WebTool.class within a cdi scoped bean.





I dont know why weld is needed for a normal static class. The class does not make use of cdi. However, the methods of the WebTool.class is used within cdi scoped beans. 


was (Author: nimo22):
Put the following class in a typcial war and start wildfly

{code:java}
import java.net.URI;
import java.net.http.HttpClient;
import java.net.http.HttpRequest;
import java.net.http.HttpResponse.BodyHandlers;
import java.time.Duration;
import java.util.Map;

import javax.ws.rs.client.Client;
import javax.ws.rs.client.ClientBuilder;
import javax.ws.rs.client.Entity;
import javax.ws.rs.client.Invocation;
import javax.ws.rs.client.WebTarget;
import javax.ws.rs.core.MultivaluedHashMap;
import javax.ws.rs.core.MultivaluedMap;
import javax.ws.rs.core.Response;

import org.jboss.logging.Logger;

public final class WebTool {

	private WebTool(){}
	
	private static Logger log = Logger.getLogger(WebTool.class);

	public static Response doPostRequest(Client httpClient, String uri, Entity<?> entity) {
		WebTarget target = httpClient.target(uri);
		Invocation request = target.request().buildPost(entity);
		return request.invoke();
	}

}
{code}

, then 
{code:java}
WELD-000119
{code}
 is shown in the log.

I dont know why weld is needed for a normal static class. The class does not make use of cdi. However, the methods of the WebTool.class is used within cdi scoped beans. 

> WELD-000119: Not generating any bean definitions from..class loading error: Type java.net.http.HttpClient
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-12886
>                 URL: https://issues.redhat.com/browse/WFLY-12886
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: CDI / Weld
>    Affects Versions: 17.0.1.Final
>            Reporter: nimo stephan
>            Assignee: Matěj Novotný
>            Priority: Minor
>
> I get this info when starting wildfly server:
> {code:java}
> 01:33:09,168 INFO  [org.jboss.weld.Bootstrap] WELD-000119: Not generating any bean definitions from com.utils.WebUtils because of underlying class loading error: Type java.net.http.HttpClient from [Module "deployment.myapp.war" from Service Module Loader] not found. 
> {code}
> My WebUtils.class imports:
> {code:java}
> import java.net.URI;
> import java.net.http.HttpClient;
> import java.net.http.HttpRequest;
> import java.net.http.HttpResponse.BodyHandlers;
> {code}
> Should I include java se module by myself in wildfly to remove this log?



--
This message was sent by Atlassian Jira
(v7.13.8#713008)