[
https://issues.redhat.com/browse/WFLY-12886?page=com.atlassian.jira.plugi...
]
Matěj Novotný commented on WFLY-12886:
--------------------------------------
bq. Actually, I use wildfly 17
I did try With 18 and 17 and didn't see that in either.
bq. However, all works, I dont see any errors. I dont think it`s important..
Yea, that's what I was trying to explain above. The log just tells you that your util
class won't become a CDI bean but you aren't really using it as CDI bean anywhere,
so you are safe.
You could also annotate that class with {{@Vetoed}} which will prevent Weld from trying to
make it a bean.
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)