July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12292) WEB-INF/jboss-webservices.xml is ignored

by Jaikiran Pai (Jira)

[ https://issues.jboss.org/browse/WFLY-12292?page=com.atlassian.jira.plugin... ] Jaikiran Pai commented on WFLY-12292: ------------------------------------- > Is the implementation or documentation incorrect? It's neither actually :) It just so happens that the jboss-webservices.xml is used for certain other details for a webservices deployment. Co-incidentally, that file too has a "context-root" element used to specify a context root for webservices. However, in your case, where you are just a simple web application, the right configuration file is the jboss-web.xml. Which too exposes the context-root element. That's the right place to configure this value for it to be used to allow web access for your application, at the context you desire. > WEB-INF/jboss-webservices.xml is ignored > ---------------------------------------- > > Key: WFLY-12292 > URL: https://issues.jboss.org/browse/WFLY-12292 > Project: WildFly > Issue Type: Bug > Components: Documentation > Affects Versions: 17.0.1.Final > Environment: Docker > Reporter: André Kornetzky > Priority: Trivial > Labels: docs > > I wanted to change the context root of my application in the Docker image and the procedure described in the guide did not work. > https://docs.wildfly.org/17/Developer_Guide.html#configuration-through-de... > The problem can also be reproduced in the local development environment (Win 10, Eclipse, Wildlfy 2019-06). > However, it works if I create a WEB-INF/*jboss-web.xml* instead of WEB-INF/-jboss-webservices.xml-. > Is the implementation or documentation incorrect? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-3953) DMN UX - overlay validation error reporting

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3953?page=com.atlassian.jira.plugi... ] Daniele Zonca commented on DROOLS-3953: --------------------------------------- [~uxdlc] For me is the same, I don't have a strong opinion about that and I don't know what is technically feasible on DMN editor side. I expect is doable but I think this will be evaluated in a further phase > DMN UX - overlay validation error reporting > ------------------------------------------- > > Key: DROOLS-3953 > URL: https://issues.jboss.org/browse/DROOLS-3953 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam, drools-tools > Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run-popup.png, Error reporting after test run.png, ut.png, ux-decision button.png, ux-decision table.png > > > As user during DMN model editing, I want to see validation errors on the model in case of wrong FEEL expression or invalid decision table. > I want to see this kind of errors in the decisions and at diagram level. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-827) Document docker registries

by Jeeva Kandasamy (Jira)

[ https://issues.jboss.org/browse/SWSQE-827?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy commented on SWSQE-827: --------------------------------------- [~gbaufake] [~fbrychta] I have updated for Jeager images. > Document docker registries > -------------------------- > > Key: SWSQE-827 > URL: https://issues.jboss.org/browse/SWSQE-827 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > Istio/Kiali/Jaeger images/operator images are located in different docker registries with different tags. > We need to document all used registries such as: > * https://quay.io/repository/kiali/kiali-operator > * https://quay.io/repository/kiali/kiali > * https://quay.io/repository/kiali-qe/kiali > * https://quay.io/repository/kiali-qe/kiali-operator > * https://quay.io/repository/kiali-qe/operator > * quay.io/maistra/* > Tags like: > * latest-qe in quay.io/maistra > We need to document what are downstream/upstream images. Usage of tags, official images vs. qe images etc. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12292) WEB-INF/jboss-webservices.xml is ignored

by André Kornetzky (Jira)

André Kornetzky created WFLY-12292: -------------------------------------- Summary: WEB-INF/jboss-webservices.xml is ignored Key: WFLY-12292 URL: https://issues.jboss.org/browse/WFLY-12292 Project: WildFly Issue Type: Bug Components: Documentation Affects Versions: 17.0.1.Final Environment: Docker Reporter: André Kornetzky I wanted to change the context root of my application in the Docker image and the procedure described in the guide did not work. https://docs.wildfly.org/17/Developer_Guide.html#configuration-through-de... The problem can also be reproduced in the local development environment (Win 10, Eclipse, Wildlfy 2019-06). However, it works if I create a WEB-INF/*jboss-web.xml* instead of WEB-INF/-jboss-webservices.xml-. Is the implementation or documentation incorrect? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-827) Document docker registries

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-827?page=com.atlassian.jira.plugin.... ] Filip Brychta reassigned SWSQE-827: ----------------------------------- Assignee: Filip Brychta > Document docker registries > -------------------------- > > Key: SWSQE-827 > URL: https://issues.jboss.org/browse/SWSQE-827 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > Istio/Kiali/Jaeger images/operator images are located in different docker registries with different tags. > We need to document all used registries such as: > * https://quay.io/repository/kiali/kiali-operator > * https://quay.io/repository/kiali/kiali > * https://quay.io/repository/kiali-qe/kiali > * https://quay.io/repository/kiali-qe/kiali-operator > * https://quay.io/repository/kiali-qe/operator > * quay.io/maistra/* > Tags like: > * latest-qe in quay.io/maistra > We need to document what are downstream/upstream images. Usage of tags, official images vs. qe images etc. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-827) Document docker registries

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-827?page=com.atlassian.jira.plugin.... ] Filip Brychta commented on SWSQE-827: ------------------------------------- Added following doc: https://docs.jboss.org/display/SWSQE/Container+images+registries > Document docker registries > -------------------------- > > Key: SWSQE-827 > URL: https://issues.jboss.org/browse/SWSQE-827 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Priority: Major > Labels: infrastructure > > Istio/Kiali/Jaeger images/operator images are located in different docker registries with different tags. > We need to document all used registries such as: > * https://quay.io/repository/kiali/kiali-operator > * https://quay.io/repository/kiali/kiali > * https://quay.io/repository/kiali-qe/kiali > * https://quay.io/repository/kiali-qe/kiali-operator > * https://quay.io/repository/kiali-qe/operator > * quay.io/maistra/* > Tags like: > * latest-qe in quay.io/maistra > We need to document what are downstream/upstream images. Usage of tags, official images vs. qe images etc. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12290) Class ava.net.HttpClient not found in Wildfly 17

by Jaikiran Pai (Jira)

[ https://issues.jboss.org/browse/WFLY-12290?page=com.atlassian.jira.plugin... ] Jaikiran Pai updated WFLY-12290: -------------------------------- Component/s: Class Loading > Class ava.net.HttpClient not found in Wildfly 17 > ------------------------------------------------ > > Key: WFLY-12290 > URL: https://issues.jboss.org/browse/WFLY-12290 > Project: WildFly > Issue Type: Bug > Components: Class Loading > Affects Versions: 17.0.1.Final > Environment: Development: Win 10, JDK 11, Eclipse 2019-06 > Reporter: André Kornetzky > Assignee: Brian Stansberry > Priority: Minor > Labels: Modules, jdk11 > > When I deploy my war module, I get the following error: > Caused by: java.lang.ClassNotFoundException: java.net.http.HttpClient from [Module "deployment.webservice-impl-1-3.0.0.war" from Service Module Loader] > In the same environment is also a Wildfly 16.0.0 installed. There the war module starts without errors. > In the discussion on https://developer.jboss.org/message/990207?et=watches.email.thread#990207 it was said that this was not considered by the upgrading of the JBoss module: > https://github.com/wildfly/wildfly-core/commit/fc649ab01eff81c55084d241fb... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12290) Class java.net.HttpClient not found in Wildfly 17

by Jaikiran Pai (Jira)

[ https://issues.jboss.org/browse/WFLY-12290?page=com.atlassian.jira.plugin... ] Jaikiran Pai updated WFLY-12290: -------------------------------- Summary: Class java.net.HttpClient not found in Wildfly 17 (was: Class ava.net.HttpClient not found in Wildfly 17) > Class java.net.HttpClient not found in Wildfly 17 > ------------------------------------------------- > > Key: WFLY-12290 > URL: https://issues.jboss.org/browse/WFLY-12290 > Project: WildFly > Issue Type: Bug > Components: Class Loading > Affects Versions: 17.0.1.Final > Environment: Development: Win 10, JDK 11, Eclipse 2019-06 > Reporter: André Kornetzky > Assignee: Brian Stansberry > Priority: Minor > Labels: Modules, jdk11 > > When I deploy my war module, I get the following error: > Caused by: java.lang.ClassNotFoundException: java.net.http.HttpClient from [Module "deployment.webservice-impl-1-3.0.0.war" from Service Module Loader] > In the same environment is also a Wildfly 16.0.0 installed. There the war module starts without errors. > In the discussion on https://developer.jboss.org/message/990207?et=watches.email.thread#990207 it was said that this was not considered by the upgrading of the JBoss module: > https://github.com/wildfly/wildfly-core/commit/fc649ab01eff81c55084d241fb... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-827) Document docker registries

by Filip Brychta (Jira)

Filip Brychta created SWSQE-827: ----------------------------------- Summary: Document docker registries Key: SWSQE-827 URL: https://issues.jboss.org/browse/SWSQE-827 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Istio/Kiali/Jaeger images/operator images are located in different docker registries with different tags. We need to document all used registries such as: * https://quay.io/repository/kiali/kiali-operator * https://quay.io/repository/kiali/kiali * https://quay.io/repository/kiali-qe/kiali * https://quay.io/repository/kiali-qe/kiali-operator * https://quay.io/repository/kiali-qe/operator * quay.io/maistra/* Tags like: * latest-qe in quay.io/maistra We need to document what are downstream/upstream images. Usage of tags, official images vs. qe images etc. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-4282) Remove use of java.security.acl APIs in Elytron PolicyDefinitions

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4282?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4282: -------------------------------- Fix Version/s: (was: 10.0.0.Beta1) > Remove use of java.security.acl APIs in Elytron PolicyDefinitions > ----------------------------------------------------------------- > > Key: WFCORE-4282 > URL: https://issues.jboss.org/browse/WFCORE-4282 > Project: WildFly Core > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Priority: Critical > Labels: Java13 > > The 'java.security.acls' packages has been deprecated and flagged for removal, this will be removed in Java 13 > https://bugs.openjdk.java.net/browse/JDK-8191138 > Within the Elytron subsystem we are presently using it within the PolicyDefinitions / Subject conversion likely to maintain compatibility with prior PicketBox implementations. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2019