December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-1046) Automate Validation links https://github.com/kiali/kiali/issues/2014

by Hayk Hovsepyan (Jira)

Hayk Hovsepyan created SWSQE-1046: ------------------------------------- Summary: Automate Validation links https://github.com/kiali/kiali/issues/2014 Key: SWSQE-1046 URL: https://issues.redhat.com/browse/SWSQE-1046 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-1045) Jenkins master configuration as a code

by Filip Brychta (Jira)

Filip Brychta created SWSQE-1045: ------------------------------------ Summary: Jenkins master configuration as a code Key: SWSQE-1045 URL: https://issues.redhat.com/browse/SWSQE-1045 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta Currently we configured jenkins master manually and we are backing it up. There is a new internal project to keep jenkins master as a code: https://docs.engineering.redhat.com/display/CentralCI/CCI+Jenkins+Declara... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBMETA-417) Update schema to show https schema URL instead of http

by Chao Wang (Jira)

Chao Wang created JBMETA-417: -------------------------------- Summary: Update schema to show https schema URL instead of http Key: JBMETA-417 URL: https://issues.redhat.com/browse/JBMETA-417 Project: JBoss Metadata Issue Type: Bug Reporter: Chao Wang Assignee: Chao Wang -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBMETA-417) Update schema to show https schema URL instead of http

by Chao Wang (Jira)

[ https://issues.redhat.com/browse/JBMETA-417?page=com.atlassian.jira.plugi... ] Chao Wang updated JBMETA-417: ----------------------------- Git Pull Request: https://github.com/jboss/metadata/pull/136 > Update schema to show https schema URL instead of http > ------------------------------------------------------ > > Key: JBMETA-417 > URL: https://issues.redhat.com/browse/JBMETA-417 > Project: JBoss Metadata > Issue Type: Bug > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

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

by Matěj Novotný (Jira)

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

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12905) Update $JBOSS_HOME/docs/schema to show https schema URL instead of http

by Chao Wang (Jira)

Chao Wang created WFLY-12905: -------------------------------- Summary: Update $JBOSS_HOME/docs/schema to show https schema URL instead of http Key: WFLY-12905 URL: https://issues.redhat.com/browse/WFLY-12905 Project: WildFly Issue Type: Bug Components: Server Affects Versions: 18.0.1.Final Reporter: Chao Wang Assignee: Chao Wang -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12905) Update $JBOSS_HOME/docs/schema to show https schema URL instead of http

by Chao Wang (Jira)

[ https://issues.redhat.com/browse/WFLY-12905?page=com.atlassian.jira.plugi... ] Chao Wang updated WFLY-12905: ----------------------------- Description: jboss.org will start redirecting http to https , while JBoss should not have an issue if deployment descriptors are referencing http when they get redirected, we have seen some frameworks do have an issue. So it would be better if our schemas tell users to use the https for the schema. > Update $JBOSS_HOME/docs/schema to show https schema URL instead of http > ----------------------------------------------------------------------- > > Key: WFLY-12905 > URL: https://issues.redhat.com/browse/WFLY-12905 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 18.0.1.Final > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Major > > jboss.org will start redirecting http to https , while JBoss should not have an issue if deployment descriptors are referencing http when they get redirected, we have seen some frameworks do have an issue. So it would be better if our schemas tell users to use the https for the schema. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1915) stronger credential store

by Hisanobu Okuda (Jira)

Hisanobu Okuda created ELY-1915: ----------------------------------- Summary: stronger credential store Key: ELY-1915 URL: https://issues.redhat.com/browse/ELY-1915 Project: WildFly Elytron Issue Type: Feature Request Components: Credential Store Affects Versions: 1.6.1.Final Reporter: Hisanobu Okuda JCEKS which is used for credential store uses 3DES. Need more stronger credential store based on a stronger cryptography like AES256 or more. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 1 month

1
0
0 / 0

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

by nimo stephan (Jira)

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

5 years, 1 month

1
0
0 / 0

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

by nimo stephan (Jira)

[ https://issues.redhat.com/browse/WFLY-12886?page=com.atlassian.jira.plugi... ] nimo stephan commented on WFLY-12886: ------------------------------------- >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)

5 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2019