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

[Matěj Novotný (Jira)]

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

Matěj Novotný commented on WFLY-12886:
--------------------------------------

bq. I dont know why weld is needed for a normal static class. 

Aren't you using empty {{beans.xml}}? Because in that case a CDI discovery mode {{all}} is used and Weld will try to convert all possible classes into beans meaning it will attempt to do just that for your {{WebTool}} class as well.

> 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)