[
https://issues.redhat.com/browse/WFLY-12886?page=com.atlassian.jira.plugi...
]
nimo stephan edited comment on WFLY-12886 at 12/19/19 5:03 PM:
---------------------------------------------------------------
Aren't you using empty beans.xml?
yes, my beans.xml is emtpy.
Hmm, I cannot reproduce the problem.
Actually, I use wildfly 17..and I see "WELD-000119" *on every log on restart.*.I
cannot confirm this on wf 18..I also enabled DEBUG log to see more:
{code:java}
..
03:22:14,144 INFO [io.smallrye.metrics] MicroProfile: Metrics activated
03:22:14,185 WARN [org.jboss.weld.Bootstrap] WELD-000146:
BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class
com.sun.faces.flow.FlowDiscoveryCDIHelper is deprecated from CDI 1.1!
03:22:14,485 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. If this is unexpected, enable DEBUG logging to see the full error.
03:22:15,508 DEBUG [org.jboss.as.jpa] ServerService Thread Pool -- 81:transaction scoped
EntityManager [ki.war#PU_QI]: created entity manager session Local transaction
(delegate=TransactionImple < ac, BasicAction: 0:ffff7f000001:50467e87:5dfadec2:11
status: ActionStatus.RUNNING >, owner=Local transaction context for provider JBoss JTA
transaction provider)
..
{code}
However, all works, I dont see any errors. I dont think it`s important..
was (Author: nimo22):
Aren't you using empty beans.xml?
yes, my beans.xml is emtpy.
Hmm, I cannot reproduce the problem.
Actually, I use wildfly 17..and I see "WELD-000119" on every log on restart..I
cannot confirm this on wf 18..I also enabled DEBUG log to see more:
{code:java}
..
03:22:14,144 INFO [io.smallrye.metrics] MicroProfile: Metrics activated
03:22:14,185 WARN [org.jboss.weld.Bootstrap] WELD-000146:
BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class
com.sun.faces.flow.FlowDiscoveryCDIHelper is deprecated from CDI 1.1!
03:22:14,485 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. If this is unexpected, enable DEBUG logging to see the full error.
03:22:15,508 DEBUG [org.jboss.as.jpa] ServerService Thread Pool -- 81:transaction scoped
EntityManager [ki.war#PU_QI]: created entity manager session Local transaction
(delegate=TransactionImple < ac, BasicAction: 0:ffff7f000001:50467e87:5dfadec2:11
status: ActionStatus.RUNNING >, owner=Local transaction context for provider JBoss JTA
transaction provider)
..
{code}
However, all works, I dont see any errors. I dont think it`s important..
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)