August 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13740) Upgrade Narayana to 5.10.6.Final

by Bartosz Spyrko-Smietanko (Jira)

[ https://issues.redhat.com/browse/WFLY-13740?page=com.atlassian.jira.plugi... ] Bartosz Spyrko-Smietanko updated WFLY-13740: -------------------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/13308) > Upgrade Narayana to 5.10.6.Final > -------------------------------- > > Key: WFLY-13740 > URL: https://issues.redhat.com/browse/WFLY-13740 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Bartosz Spyrko-Smietanko > Assignee: Ondrej Chaloupka > Priority: Major > Fix For: 20.0.0.Beta1, 20.0.0.Final > > > Component upgrade of Narayana to version 5.10.5.Final. > This version provides the capability for CDI interceptors of context propagation and async handling. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13740) Upgrade Narayana to 5.10.6.Final

by Bartosz Spyrko-Smietanko (Jira)

Bartosz Spyrko-Smietanko created WFLY-13740: ----------------------------------------------- Summary: Upgrade Narayana to 5.10.6.Final Key: WFLY-13740 URL: https://issues.redhat.com/browse/WFLY-13740 Project: WildFly Issue Type: Component Upgrade Components: Transactions Reporter: Bartosz Spyrko-Smietanko Assignee: Ondrej Chaloupka Fix For: 20.0.0.Beta1, 20.0.0.Final Component upgrade of Narayana to version 5.10.5.Final. This version provides the capability for CDI interceptors of context propagation and async handling. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13739) WeldJpaInjectionTestCase fails in the jpa layer test suite

by Yeray Borges Santana (Jira)

[ https://issues.redhat.com/browse/WFLY-13739?page=com.atlassian.jira.plugi... ] Yeray Borges Santana updated WFLY-13739: ---------------------------------------- Summary: WeldJpaInjectionTestCase fails in the jpa layer test suite (was: WeldJpaInjectionTestCase fails when we are using jpa layer) > WeldJpaInjectionTestCase fails in the jpa layer test suite > ---------------------------------------------------------- > > Key: WFLY-13739 > URL: https://issues.redhat.com/browse/WFLY-13739 > Project: WildFly > Issue Type: Bug > Components: Build System, JPA / Hibernate, Test Suite > Reporter: Yeray Borges Santana > Assignee: Yeray Borges Santana > Priority: Major > > We removed the microprofile-metrics from jpa layers. This removal affected to WeldJpaInjectionTestCase test execution, which uses CDI to inject beans. > This test was being executed with combining jpa and datasources-web-server, however, datasources-web-server does not add CDI. We need to use the upper base layer to make the test pass. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13739) WeldJpaInjectionTestCase fails when we are using jpa layer

by Yeray Borges Santana (Jira)

[ https://issues.redhat.com/browse/WFLY-13739?page=com.atlassian.jira.plugi... ] Yeray Borges Santana updated WFLY-13739: ---------------------------------------- Component/s: Build System JPA / Hibernate Test Suite Description: We removed the microprofile-metrics from jpa layers. This removal affected to WeldJpaInjectionTestCase test execution, which uses CDI to inject beans. This test was being executed with combining jpa and datasources-web-server, however, datasources-web-server does not add CDI. We need to use the upper base layer to make the test pass. was: We removed the microprofile-metrics from jpa layers. This removal affected to WeldJpaInjectionTestCase test execution, which uses CDI to inject beans. This test were being executed with combining jpa and datasources-web-server, however, datasources-web-server does not add CDI. We need to use the upper base layer to make the test pass. > WeldJpaInjectionTestCase fails when we are using jpa layer > ---------------------------------------------------------- > > Key: WFLY-13739 > URL: https://issues.redhat.com/browse/WFLY-13739 > Project: WildFly > Issue Type: Bug > Components: Build System, JPA / Hibernate, Test Suite > Reporter: Yeray Borges Santana > Assignee: Yeray Borges Santana > Priority: Major > > We removed the microprofile-metrics from jpa layers. This removal affected to WeldJpaInjectionTestCase test execution, which uses CDI to inject beans. > This test was being executed with combining jpa and datasources-web-server, however, datasources-web-server does not add CDI. We need to use the upper base layer to make the test pass. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13739) WeldJpaInjectionTestCase fails when we are using jpa layer

by Yeray Borges Santana (Jira)

Yeray Borges Santana created WFLY-13739: ------------------------------------------- Summary: WeldJpaInjectionTestCase fails when we are using jpa layer Key: WFLY-13739 URL: https://issues.redhat.com/browse/WFLY-13739 Project: WildFly Issue Type: Bug Reporter: Yeray Borges Santana Assignee: Yeray Borges Santana We removed the microprofile-metrics from jpa layers. This removal affected to WeldJpaInjectionTestCase test execution, which uses CDI to inject beans. This test were being executed with combining jpa and datasources-web-server, however, datasources-web-server does not add CDI. We need to use the upper base layer to make the test pass. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13737) Upgrade wildfly-transaction-client from 1.1.11.Final to 1.1.13.Final

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/WFLY-13737?page=com.atlassian.jira.plugi... ] Ondrej Chaloupka reassigned WFLY-13737: --------------------------------------- Assignee: Tomasz Adamski (was: Ondrej Chaloupka) > Upgrade wildfly-transaction-client from 1.1.11.Final to 1.1.13.Final > -------------------------------------------------------------------- > > Key: WFLY-13737 > URL: https://issues.redhat.com/browse/WFLY-13737 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Chao Wang > Assignee: Tomasz Adamski > Priority: Major > > Tag: https://github.com/wildfly/wildfly-transaction-client/releases/tag/1.1.13... > Diff: https://github.com/wildfly/wildfly-transaction-client/compare/1.1.11.Fina... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13676) Increase the test coverage of jpa and jpa-distributed galleon layers

by Yeray Borges Santana (Jira)

[ https://issues.redhat.com/browse/WFLY-13676?page=com.atlassian.jira.plugi... ] Yeray Borges Santana updated WFLY-13676: ---------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/13424 (was: https://github.com/wildfly/wildfly/pull/13424, https://github.com/wildfly/wildfly/pull/13440) > Increase the test coverage of jpa and jpa-distributed galleon layers > -------------------------------------------------------------------- > > Key: WFLY-13676 > URL: https://issues.redhat.com/browse/WFLY-13676 > Project: WildFly > Issue Type: Task > Components: Build System, JPA / Hibernate, Test Suite > Reporter: Yeray Borges Santana > Assignee: Yeray Borges Santana > Priority: Major > Fix For: 21.0.0.Beta1 > > > These layers must be tested independently on testsuite/layers testsuite. > These layers should also be tested in aggregation with one or more base layers it is expected to decorate, running the test with each of one separately. > We have to add new Galleon provision execution to provision a server with a base layer provisioned with jpa or jpa-distributed and add a surefire execution to run suitable WildFly tests on them. > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-324) Bootable JAR - Add an alternative way to the CLI in order to configure the server

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFWIP-324?page=com.atlassian.jira.plugin... ] Darran Lofthouse commented on WFWIP-324: ---------------------------------------- I was questioning something similar myself. Galleon in itself is not a configuration tool, it is a tool to assemble "layers" of functionality into a running server making a defined set of features available. Configuration creeps in a bit as we need things like selecting between legacy security and Elytron security, but anything beyond that is not what Galleon and the layers were intended to solve. As an example I am contributing an example to the bootable jar project to enable username / password authentication for a deployment - at the moment this will lead to numerous CLI commands to achieve but it feels like there may be a middle ground of common tasks / use cases that could fit somewhere between layers and CLI scripts. > Bootable JAR - Add an alternative way to the CLI in order to configure the server > --------------------------------------------------------------------------------- > > Key: WFWIP-324 > URL: https://issues.redhat.com/browse/WFWIP-324 > Project: WildFly WIP > Issue Type: Enhancement > Reporter: Fabio Burzigotti > Assignee: Jean Francois Denise > Priority: Major > > Using the CLI to configure the packaged server seems not to be the optimal or final solution, since it reveals implementation details about the runtime and its usage is not immediate. > Furthermore that configuration makes POM definition more cumbersome IMHO. > This WFWIP is to discuss an enhancement as an alternative to the CLI scripts for a static configuration of the server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-324) Bootable JAR - Add an alternative way to the CLI in order to configure the server

by Fabio Burzigotti (Jira)

Fabio Burzigotti created WFWIP-324: -------------------------------------- Summary: Bootable JAR - Add an alternative way to the CLI in order to configure the server Key: WFWIP-324 URL: https://issues.redhat.com/browse/WFWIP-324 Project: WildFly WIP Issue Type: Enhancement Reporter: Fabio Burzigotti Assignee: Jean Francois Denise Using the CLI to configure the packaged server seems not to be the optimal or final solution, since it reveals implementation details about the runtime and its usage is not immediate. Furthermore that configuration makes POM definition more cumbersome IMHO. This WFWIP is to discuss an enhancement as an alternative to the CLI scripts for a static configuration of the server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10929) Unescaped characters in URL from client does not work correctly when allowed for HTTP and HTTPS listeners

by Carlo de Wolf (Jira)

[ https://issues.redhat.com/browse/WFLY-10929?page=com.atlassian.jira.plugi... ] Carlo de Wolf commented on WFLY-10929: -------------------------------------- https://tools.ietf.org/html/rfc7540#section-3.2 https://tools.ietf.org/html/rfc7230#section-2.7.1 https://tools.ietf.org/html/rfc3986#section-3.2.1 URL should be percentage-encoded, while log is probably UTF-8 encoded. How can the access log then be expected to show non UTF-8 characters? > Unescaped characters in URL from client does not work correctly when allowed for HTTP and HTTPS listeners > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-10929 > URL: https://issues.redhat.com/browse/WFLY-10929 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 14.0.0.Beta2 > Reporter: Jan Stourac > Assignee: Bartosz Baranowski > Priority: Major > Attachments: helloworld.war > > > Since the time of {{EAP7.1.1.CP}} there is a possibility to allow unescaped characters in URL requests from clients to server. This was allowed first by setting {{org.wildfly.undertow.ALLOW_UNESCAPED_CHARACTERS_IN_URL=true}} system property introduced by UNDERTOW-1185. Now we have a new attribute for this in Wildfly in AJP, HTTP and HTTPS listeners {{allow-unescaped-characters-in-url}}. > However this does not seem to work correctly. There have been some fixes for AJP listener already UNDERTOW-1386, UNDERTOW-1386 and UNDERTOW-1399 (the last one not included in WildFly {{14.0.0.Beta2}} yet). However HTTP/HTTPS listener seems to be broken too. > When HTTP request with unescaped characters is performed against server: > {code} > curl "http://localhost:8080/helloworld/한글이름_test.html?param=한글이름_ahoy" -v >/dev/null > {code} > we get 200 OK HTTP response, although the result in access log looks like: > {code:title=HTTP actual result} > 127.0.0.1 - - [27/Aug/2018:09:17:39 +0200] "GET /helloworld/íê¸ì´ë¦ > _test.html?param=íê¸ì´ë¦ > _ahoy HTTP/1.1" 200 950 > {code} > but we expect following: > {code:title=HTTP expected result} > 127.0.0.1 - - [27/Aug/2018:08:40:47 +0200] "GET /helloworld/한글이름_test.html?param=한글이름_ahoy HTTP/1.1" 200 950 > {code} > Slightly different problem seems to be also for HTTPS listener. When we perform HTTPS request against WildFly: > {code} > curl "https://localhost:8443/helloworld/한글이름_test.html?param=한글이름_ahoy" -v >/dev/null --insecure > {code} > we receive 404 Not Found HTTP response and following record in access.log: > {code:HTTPS actual result} > 127.0.0.1 - - [27/Aug/2018:09:18:37 +0200] "GET /helloworld/￭ﾕﾜ￪ﾸﾀ￬ﾝﾴ￫ﾦﾄ_test.html?param=￭ﾕﾜ￪ﾸﾀ￬ﾝﾴ￫ﾦﾄ_ahoy HTTP/2.0" 404 68 > {code} > however expected result should be similar to what we expect for HTTP, I guess. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

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 August 2020